Permission management

System, resource and environment

The register separates systems or resource groups, specific resources and environments. Access can cover a selected repository, database or server, in a test or production environment.

Specify a single resource and environment, or cover all of them in one entry. The table shows the employee and their exact access scope.

Requests and decisions

An employee or authorised person submits a request with a defined access scope. The person responsible records the decision, and the entry receives its current status.

• Pending requests can be approved or rejected.
• Granted access can be revoked.
• Each decision records who acted and when.
• Roles determine who can request, approve, reject and revoke access.

Many access entries at once

Select several entries and approve, reject or revoke them in bulk. Every change remains in the history of the relevant access entry.

Expiry dates

Granted access has an expiry date based on the system or project configuration. Date indicators help you find entries that will expire soon.

Access history and review

Open an entry's action history with people and dates. Filter the table by employee, requester, person taking action, status and date range.

Search also covers project, resource and environment names. Active filters are saved in the page address, so you can return to the same view or share its link with another authorised person.

Tasks for the people managing access

Once connected to Projects, access changes can create tasks. The description includes the employee, system, resource, environment and whether access is being granted or revoked.

The register handles requests and records decisions. Applying access in an external system remains the work of the people responsible for it.