How to Give Jira Access to User, Provide Dashboard Access in Projects Easily 2026

User access in Jira isn't managed from inside a project — it starts at the organization level. Click the gear icon in the top-right corner of Jira to reach Settings, which is also where Atlassian surfaces account-wide features like Jira Service Management. From here you're one click from the Admin area that lists every user and product in your organization, so this is the starting point any time you need to add, remove, or audit access.

From the admin area, use Invite users to open the invite form. Type the person's email address and you'll see a table listing every app in your organization — Projects, Goals, Jira, Jira Product Discovery, Confluence, and so on — each with its own Role dropdown defaulted to User.

Leave the defaults if they need standard access, or narrow individual apps down before sending. Jira emails the recipient asking them to complete their account, so nothing is granted until they accept.

After sending the invite, head back to Admin > Users to verify it went through. The new account shows an Invited status until accepted, at which point it flips to Active. This screen is also your ongoing roster: it shows total users, active users, and organization admins at a glance, and you can search by name or filter by role and app access whenever you need to check who currently has access to what.

Being invited to the organization doesn't put someone inside a project — that's a separate step, done from within the project itself, at Project settings > Access (sometimes labelled People), using Add people to search by name or email. What roles you're offered here depends on the kind of project.

The Administrator, Creator, and Contributor set pictured below is specific to Jira Product Discovery: Administrator gives full control including people and settings, Creator can use every feature except admin-only settings, and Contributor gets read-only access plus the ability to add ideas, comments, and reactions. A standard Jira Software or Jira Work Management project instead offers whatever roles your site's permission scheme defines, commonly Administrators and Members, so don't assume this exact three-tier list will appear on every project type — check what's actually in the dropdown and pick the narrowest role that still lets the person do their job.

Project access controls boards and issues, but dashboards are shared separately. Open the dashboard, select More actions > Rename or share, and add the individual, a group, or the whole project under Viewers or Editors.

This is what actually lets a new teammate see burndown charts, sprint reports, or custom gadgets without you walking them through building their own. Sharing a dashboard needs its own permission — Share dashboards and filters — so if that option is missing for you, an admin will need to either grant it or share the dashboard on your behalf.

Once the invite, project role, and dashboard sharing are all in place, take thirty seconds to log in as a test or ask the new user to confirm what they can see. Grant only what someone's role genuinely requires. An admin role for a contributor-level task is over-provisioning that becomes a security headache later, and it's far easier to widen access when it's actually needed than to track down and revoke it afterward.