Affected: Roles, Custom Roles
Symptoms
When a team member signs in to LaunchDarkly, they receive the following message:
"Your administrator hasn’t given you permission to do anything yet.
To use LaunchDarkly, contact your manager or administrator.
You can also sign out and authenticate with a different account."
Cause
This issue occurs when:
- The team member has a No access built-in role.
- The team member is assigned a custom role that was created using the No access role as its starting point.
Note: Custom roles created before October 2024 could use the built-in Reader role as a starting point. Since October 2024, all new custom roles start with No access by default. If a member has permission to modify a resource but lacks permission to view the project it belongs to, they will not be able to make changes because they cannot see it.
Solution
For team members (non-admins):
Contact your administrator and request appropriate access permissions.
For admins:
-
Locate the affected team member.
-
Check their assigned role.
-
If the team member has the built-in No access role:
-
Assign them a different built-in or custom role with appropriate permissions.
-
- If the team member has a custom role and should have access, follow one of these options:
Option 1: Use the Advanced editor
Add the following statement to the custom role to grant project view access:
Replace "proj/*"
with a specific project key if you want to restrict access to a single project.
Option 2: Use the Role builder
-
Locate the custom role and click View role.
-
Click the pencil icon to edit it.
-
Add the
viewProject
action. -
Apply it to all projects or a specific project.
-
Click Update role.
Example:

After you update the permissions, ask the team member to log in again.
If the issue persists, contact LaunchDarkly Support.