Overview

EFS can restrict access to individual projects by assigning project access rights to one or more teams.^[1][2]

If a project’s access rights are changed so that none of your teams have access anymore, you may not be able to manage that project until a team you are a member of is granted access again.^[1][2]

Solution

Goal: A user with sufficient rights grants your team read and (if needed) write rights to the project again.^[1]

Option A (self-service if another admin still has access): Re-grant project rights in the EFS UI

1. Sign in to the EFS admin area with an account that can access the project list.^[1]
2. Go to Projects and locate the project in the list.^[1]
3. Open Further actions for the project, then select Rights.^[1]
4. Grant the required team(s) read access (and write access if editing is required).^[1]
5. Save/confirm the change in the rights administration dialog.^[1]

Option B (when no one on your side can access the project rights): Contact Support

If nobody in your organization can reach the project’s Rights administration screen, ask Support to restore access. Provide:

• Instance URL.
• Project name and/or project ID.
• The team(s) that should receive project access, and whether you need read only or read + write.
• The usernames/emails of the users who must regain access.

<supportagent>

Project access is managed via team-based rights and object rights. If the customer removed all project rights (or removed the only team that could access the project), use the project rights administration flow from Projects → Further actions → Rights to add back a team with read/write access that includes the affected admin user so they can recover the project in the UI.^[1][2][3]

</supportagent>

References

1. Projects
2. Options
3. Overview of ACL Rights