User Access Maintenance

Each PAMMS Project contains a users.yaml file that is to maintain users access rights to the project. The process for updating this file is similar to updating a Policy and will go through the standard process to merge the update.

A different Pipeline runs when the users.yaml is updated to update access rights to the users in the file. Due to the difference in Pipelines when updating the users.yaml file no other files should be updated in the same Merge Request.

User Maintenance

The users.yaml file contains a list of users for that project and what their specific role is for that project. If a user is listed in the file when the pipeline runs they will be granted the role assigned. The structure of the file is shown below.

Users:
  - username: john.smith
    role: developer

  - username: jane.smith
    role: developer

  • username: Should be the individuals GitLab username.

  • role: Is the role to be granted to that user. The standard role for a Policy Maintainer should be developer.

User Guides

FAQ

  1. How to find your GitLab Username?

    On the main GitLab page click on the profile icon, as seen below, to open user menu. Your username is below your formal name.

    view-user-name

  2. Will updates to user access still require approval?

    Yes, the update will require the standard approval process.

  3. Can you add and remove a user in a single update?

    Yes, it is possible to combine addition and removal of users into the same Issue.