Access Permissions And Security

Question 1

Default config of a Kanban company-managed Notification Scheme

Answer 1

All watchers, Current assignee, and Reporter

Question 2

Can users view issues created prior to a change in permissions?

Answer 2

No

Question 3

Do team managed projects use Issue Security Levels/Schemes?

Answer 3

No, it uses access levels

Question 4

Team managed access levels

Answer 4

• Open –> anyone can view and create issues on the project ( anyone who logs in)
• Limited –> view and comment
• Private –> only people added to project can view issues

Question 5

What exists in Jira Cloud that doesn’t exist in Jira Server/Data-Center

Answer 5

Team managed projects

Question 6

The three admin types:

Answer 6

org admin, Jira admin, project admin

Question 7

Org Admin

Answer 7

configure organisation wide settings:
* Billing and product subscriptions,
* verifying or removing domains
* configuring managed accounts, users, groups product access

When you create an organisation, you become an organisation admin and automatically get admin permissions in Jira.

Question 8

What are the global permissions

Answer 8

Administer Jira
Browse users and groups
Share dashboards and filters
Manage group filter subscriptions
Make bulk changes
Create team-managed projects

Question 9

Team managed default roles:

Answer 9

• Administrator
• Member
• Viewer

Question 10

Product admin

Answer 10

administer product settings.

You have access to the system administration menus and configure project schemes.

Question 11

What permissions are needed to Log Work?

Answer 11

Browse Projects, Edit Issues and Work on issues.

Question 12

What permissions are needed to Edit Issues?

Answer 12

Browse Projects, Edit Issues

Question 13

Product admins what do they do ?

Answer 13

They administer settings inside the product depending on group memberships. ( don’t have product access)

NOTE: Product admins for Jira products have product access to Jira or Jira Service Management.

Question 14

Product Admin (Jira Administrator role)

Answer 14

Product Admin (Jira Administrator role)

allows them to create and manage projects without having access to all global administration features.

This role typically allows the user to manage project configurations, workflows, schemes, etc., without giving them access to critical global settings like user management or site-wide permissions.This role doesn’t grant access to the product.

They administer users and groups from admin.atlassian.com for a specific product in your organization.

Question 15

What needs to be done before Atlassian guard can be enabled

Answer 15

Verify your organisations domain

Question 16

What permissions are needed to create versions?

Answer 16

Be project admin

Question 17

Why wouldn’t a user be able to use their Atlassian credentials anymore?

Answer 17

Their email domain might have been verified. They’ll be redirected to their org identity provider when they attempt to login to the cloud.

Question 18

Do invitation links require admin approval?

Answer 18

No

Question 19

What can board admins do?

Answer 19

Configure columns, swimlanes, card colours, issue details view etc..

Question 20

Managed accounts:

If a user has an e-mail address with a domain that your company hasn’t verified what haapens ?

Answer 20

The user’s account is unmanaged and the user doesn’t appear on your Managed Accounts page and you are unable to edit their account details.

( Its the same with accounts that have unverified Email addresses )

Question 21

What is product access ?

Answer 21

• Allows login and access to a Jira Product
• You can have multiple default acess groups
• New users can get access through these default groups

Question 22

who can edit permissions schemes ?

Answer 22

Jira Administrators are the only ones

Question 23

Groups AND Roles can be used in:

Answer 23

Permission schemes
Notification schemes

Question 24

Roles cant be used in:

Answer 24

Product acess and global permissions

Question 25

When to use group over role ?

Answer 25

if many projects share a scheme and the number of users is small and never changes.

Question 26

When to use a role over a group?

Answer 26

many users they change often they vary by project project administrators Should be able to make changes

Question 27

What to investigate if user can see and issue but not another in a project?

Answer 27

* Issue level * Issue Security scheme * Security levels * Groups Roles

Question 28

What permissions are needed to migrate from one project to another?

Answer 28

Move issues Create issues Edit issues

Question 29

What to investigate if user can see a software board but not another ?

Answer 29

A user can see one software board but not another then can they see the project? If not, then check Browse Projects permission at the project level Otherwise check the board filtre and with whom that filtre is shared.

Question 30

What to investigate if User cannot see any boards?

Answer 30

Check product access to Jira Software and the groups listed there. Only a Jira Software user can see the product specific features such as agile boards, development tools, or release information.

Question 31

What happens if you Suspend Access for a User ?

Answer 31

* He is suspended temporarely ( can be reinstated ) * Cannot acess any product in the organization. * Status shows as Suspended for the user listed. * Will still use up licences Useful for when user is temporarely away

Question 32

What happens if you Remove a User ?

Answer 32

* Wont be able to access product or collaborate with the team * User needs to be reinvited * Work activity and history is preserved. * can remain as an assignee * Will still consume licence

Question 33

What happens if you Deactivate an account ?

Answer 33

1. Account can no longer be used 2. Cannot log into atlassian accoutn service 3. User doesnt count towards Licence limit 4. You can still search for them 5. activity is preserved 6. shows as deactivated

Question 34

What happens if you Delete an account ?

Answer 34

1. Permanent 2. Deleted from all organizations 3. Other Atlassian services cannot be accessed 4. Side effects

Question 35

# company managed Issue level security configuration:

Answer 35

* Create issue security scheme * configure security levels * you need the Security level field on the screens * Needs to be done by a Jira Admin. You can set a default security level (optional) You can associate the security scheme to different projects

Question 36

# company managed Who can set the Issue level security?

Answer 36

Those with edit issue permission and set issue security permissions. They can set only a level they are in already.

Question 37

# Team managed Issue security configuration

Answer 37

* Issue type configuration screen ( padlock icon ) * Choose to only allow a role to view by default * Changes to default restrictions only apply to new issues

Question 37

# Team managed Who can set the Issue level security?

Answer 37

* Admins * roles that have a premission to "restrict any issue"

Question 38

Implications of issue security:

Answer 38

Secured issues are inaccessible: * boards * service management queues * search results and filters * reports and gadgets * notifications * issue links arent visible as hyper links * subtasks

Question 39

Use cases for issue security levels:

Answer 39

1. Issues should be seen only by a static set of users ( group roles) 2. Issues should be seen only by a dynamic set of users ( user in a custome field --> user picker) 3. Reporters should only see their isseus