Question about Product Access and Default Access Groups

Jill Vieregge

Currently, all Jira Software users are added into the Default Access Group (employees and contractors alike) and they have basic access. Is this group used as a landing area for new staff; or does it have to remain intact for users.

For example, a new contractor is added to the Default Access Group. Can I create a new Contractor group; remove him from the Default Access Group and have him only in the Contractor group?

Also, there's no reason to have another group defined if its just going to have the same permissions?

thx

Ste Wright

Hi @Jill Vieregge 

I think you can manage product access separate to Group membership - but it's likely not efficient to do so, especially if you have SSO/SAML or intend to use it in future.

I'd either...

1. Separate the Product Access Groups from Groups used for other access/permissions, or...
2. Add Group Product Access to other Groups (eg. Contractor Group) so you can filter users into other Groups, and still retain auto-product access

Both options can allow for a more secure method of managing the platform - either...

1. The Group only provides platform access, or access to Global Permissions, Projects, etc all users can see. You could then manage other Project access, etc using the other Groups, Project Roles, or similar.
2. The Groups provide access to the platform, and in turn, are used in Global Permissions, etc - depending on what employee type you are.

Ste