Access rights for developers

  • Release version: Xanadu
  • Updated August 1, 2024
  • 1 minute to read

    • To use Team Development, application developers must have a set of credentials for each instance in the Team Development hierarchy.

    An instance's placement in the team development hierarchy determines the credentials it requires.

    Table 1. Credentials for Team Development access
    Desired Access Credential Requirements
    Access to the Team Development application A user with the admin role on the instance you are accessing
    Right to register a remote instance One of following:
    • A user with the admin role on the instance you are registering
    • A user with the teamdev_user role on the instance you are registering
    Right to push changes to the parent instance from a development instance One of following:
    • A user with the admin role on the parent instance
    • A user with the teamdev_user role on the parent instance
    Right to compare to a registered remote instance One of following:
    • A user with the admin role on the registered development instance
    • A user with the teamdev_user role on the registered development instance
    Access to the Code Review Requests module One of following:
    • A user with the admin role on the parent instance
    • A user with the teamdev_code_reviewer role on the parent instance
    Note:
    The teamdev_user role does not grant access to the Team Development application and is not intended for developers to work on local development instances. It is intended to grant developers non-admin access to remote instances such as the parent instance or a peer development instance.