You are here: start » en » Internal Documentation » Working with projects » Request access

Request access

Situation

You want to contribute to a project, or to open a repository your account has no permission for.

Approach

Requests are recorded as a case and worked from an inbox. The request carries the context it was raised from automatically — project, wanted role, current role and the group you would have to be entered in. A request itself grants no permission.

There are three places where the request is offered. Which applies to you depends on where you are stuck.

Procedure

From inside a project, to become a contributor

  1. Open the project through Projects (German).
  2. Look for the section An diesem Projekt mitwirken. It names your current role.
  3. Choose Contributor-Zugriff anfordern.
  4. Say briefly what you want to work on, and send.

From a denied page

  1. The page explains which area is closed and which groups open it.
  2. Choose Zugang anfragen there.

From a denied repository

  1. Open the repository from Repositories.
  2. Where access is refused, the screen offers the request directly.

After sending you receive a case number. Your own open requests stay visible from the confirmation screen.

Remarks

For these requests there is no way round signing in. A role or access request names an account; without a session there is none that could be entered. Signing in is offered instead.

Two requests are exempt, and precisely the two that do not permit signing in at all — because otherwise they would be unreachable exactly when they are needed:

Request Address For what
Two-factor reset doku.php?do=wkrequest&type=MFA_RESET_REQUEST The second factor is lost; see Authenticator lost or phone broken
Help with this account doku.php?do=wkrequest Something about the account is wrong that its holder cannot correct themselves

Both are recorded as an unevidenced claim: somebody without a session can prove no account, so the login name given is an assertion and not a fact. The inbox marks such cases accordingly, and support establishes identity by another route before working them. Here too, never enter a password, a one-time code or an access token.

Where no button appears, the request is not currently possible — because the request handling is not set up on this installation, say, or a daily limit has been reached. A button that refuses on submission is deliberately not shown.

A repeat is added to the open request instead of creating a second case.

Who decides. The maintainers of the project concerned. They have a screen of their own for it — Mitglieder on the project page — and need no wiki administration rights. The request names the group to enter explicitly all the same, so that working it is a single move even where that happens elsewhere.

One exception remains: somebody who is to become a maintainer is appointed by the wiki administration. A maintainer grants reader and contributor roles; who decides beyond that is not their decision.

en/wiki/projects/request-access.txt · Last modified: by 0.0.0.0