This topic describes how to use the "Project Authorization" feature to grant project roles to users in batches.
Background
In scenarios with a large number of projects, it is costly for administrators to configure project roles for users on a per-project basis. Granting roles such as Global DBA directly results in overly broad permission scopes. With project authorization, administrators can first filter a batch of projects by tag or project name, then grant project roles to specified users in bulk, thereby controlling the permission scope while improving authorization efficiency.
Prerequisites
- An organization administrator or project administrator with cross-project authorization permissions.
Procedure
Log in to ODC, and in the left navigation bar, click User Permissions > Project Authorization.
Note
This tab is visible only to administrators with cross-project authorization permissions; regular project members cannot access it.
In the Authorize Users section, select the users you want to authorize.
- Fuzzy search by username or account name is supported.
- You can select one or more users.
In the Select Projects section, filter and select the projects you want to authorize.
- Filter by Project Name or Project Tag.
- After selecting "Project Tag", enter the tag name to search.
- The table displays three columns: Project Name, Tag, and Description.
- The page shows a counter that reads "Selected N / M Projects".
- Newly authorized users cannot be added to archived projects.
In the Unified Project Role section, select the project role you want to grant.
Available roles include: Developer, DBA, Administrator, Security Administrator, and Participant.
Click Batch Authorization to perform the batch authorization.
Authorization Rules
- Authorization results are bound to specific users, projects, and project roles; no dynamic tag-permission relationships are established.
- Existing duplicate authorizations will be automatically skipped and not recreated.
- When submitting, the system will revalidate whether the user, project, and role are valid, and whether the operator has authorization permissions.
- After authorization is completed, you can query the results in User Details, Project Members, and Audit Records.
Considerations
- Modifications or deletions of project tags do not automatically grant or revoke existing user permissions.
- Subsequent projects created with the same tag are not automatically included in the historical authorization scope.
- Tags are used only for project categorization and querying, and do not directly represent permissions.