Roles and permissions in Viva Goals

Role types in Viva Goals

Role	Description	Common Activities
Viva Goals Administrators	Viva Goals Administrators are assigned by Global admins or user admins from the Microsoft 365 admin center or Azure Active Directory. Viva Goals Administrators are users typically from the IT team (IT admins) and manage the policy settings for Viva Goals for the entire company. This role is optional. In the absence of a Viva Goals Admin, the Global admin can manage these Viva Goals policy settings for the company. For more information on assigning roles in the Microsoft 365 admin center, see Assign admin roles. Related content: Azure AD roles in the Microsoft 365 admin center	Some of the tasks managed by Viva Goals Admins are: Configuring who can create organizations within Viva Goals. - Configuring integrations available for all Viva Goals organizations in the tenant. - Controlling the URLs that can be embedded in Viva Goals Dashboards. - Has the permission to raise Product support tickets via MAC- to Microsoft's support team.
Organization admins	To understand more about Organizations, see Understand Organizations and Teams in Viva Goals. Organization administrators are members who manage the OKR process rollout for the org. In an organization, they're generally the OKR champions. They can configure OKR process properties (such as time period), add or remove users in the org, and create teams within an organization. An organization can have more than one organization administrator.	Some tasks managed by Organization Admins are - Creating OKRs for any team. - Accessing the admin settings at the org level. - Setting policy on who can add members to the org, create teams in the org, create new tags, and export OKRs from their org. - Change time-period and notification setting options.
Organization owner	Organization owners are generally the executive leader of a department/business unit/company for which the organization was created. At the time of organization creation in a tenant, the global admin or any user who has permissions to create an organization would become the organization owner of the newly created organization. This ownership can be transferred to another user in that organization in the admin section of the organization. An org can have only one org owner. Organizational owners manage members and teams. By default, they own organization-level OKRs, but organizational objectives can be owned by other members also.	Some of the tasks managed by Organization Owners are - Creating OKRs for any team. - Accessing the admin settings at the org level. - Setting policy on who can add members to the org, who can create teams in the org, who can create new tags, who can export OKRs from their org. - Changing time period and notification setting options.
Team admins	Team admins are generally OKR champions at a team level, who manage the set-up of a team that includes addition of members to the team, permission settings, notification settings, etc. A Team can have multiple team admins.	Some tasks managed by Team Admins are - Adding members to the team. - Modifying the notification schedule settings of the team. - Modifying the OKR and Initiative creation permission for their team. - Creating OKRs for their team. - Editing OKRs of their team. (This is a default activity.) - Creating teams, if the team creation policy at the org level admin console is set so that team admins can create teams.
Team owners	Teams are functional units within a Viva Goals Organization. Team owners are typically managers of a team. Team owners can be managers of people or managers of cross-functional teams. A team can have only one team owner.	Some tasks managed by Team owners are - Adding members to the team. - Modifying the notification schedule settings of the team. - Modifying the OKR and Initiative creation permission settings for the team. - Editing or making check-ins for all OKRs of the team.
Regular Members	Regular members (the default role for everyone) are typically users within an organization who want to actively participate in the OKR process. Viva Goals recommends all users be added as regular users.	Some of the tasks managed by Regular members are - Creating team-level or org-level OKRs and initiatives in teams or orgs provided they have creation access to the orgs and teams. - Editing, aligning, and making check-ins on their OKRs or the OKRs that they've created.
Observers	Observers, as opposed to Regular members, can't create, edit, or own OKRs. They have only read-only access to the entire organization. Viva Goals recommends adding all users as regular users instead of observers.	- Observers can't create, edit or align OKRs. - Observers can like comments on an OKR, share a summary of an entity page with other users, and comment on OKRs or Initiatives.

Permissions

Action	Access
Create OKRs or Initiatives	By default, any regular user is able to create team-level or organization-level OKRs or Initiatives in all levels unless an organization or a team has explicit permissions. Org admins or team admins who want to control OKR or initiative creation access for specific users can configure that access in org/team settings. The following roles always have Create OKRs or Initiatives permission: Organization-level OKRs 1. Organization Administrators 2. Organization Owner Team-level OKRs 1. Organization Administrators 2. Organization Owner 3. Team Administrators 4. Team Owner Everyone in an organization can create individual OKRs or Initiatives (OKRs that don't have a team assigned to them) except observers.
Check-in	The following users get default check-in access for OKRs: 1. OKR owner(s) 2. Creator of the OKR 3. Team Admin/Team Owner 4. Org Admin/Org Owner 5. Manager of the OKR owner 6. Owner of the parent OKR (the OKR with which this OKR is aligned) OKR owners also can grant users check-in access by making them check-in owners.
Alignment	By default, any regular users in an organization can align to any OKR. OKR owners can manage who can check-in on an OKR they own by granting users alignment access.
Edit	Users with edit access to an OKR can also perform the following functions on an OKR: 1. Delete  2. Modify weights and rollups 3. Close 4. Reopen The following users get default edit access for OKRs: 1. OKR owner(s) 2. Creator of the OKR 3. Team Admin/Team Owner 4. Org Admin/Org Owner 5. Manager of the OKR owner: 6. Owner of the parent O/KR (the OKR with which this OKR is aligned to) In addition, by modifying permissions to OKRs they own, OKR owners can grant users edit access. Note: A delegate is a user who can perform all the functions of a user with edit access except change the owner for an OKR or Initiative.
Clone	Users can clone OKR into a team in which they have access to create OKRs. If the users don't have creation permission access, the OKR is cloned as an individual OKR (not associated with a team).
Comment/Share/Like/Follow	Any user who is a part of an organization can perform these actions.