Configure OKR create permissions
Create organizational level permissions for OKRs and Initiatives
An administrator can set Create permissions to so the following user types, listed in greater detail below, can create OKRs and initiatives at an organization level and at a team level.
Administrators can set permissions so the following users within an organization can create OKRs and initiative. See the FAQ for specific admin types.
- Anyone in the organization: This is a good option for smaller organizations with evolving OKR needs.
- Organization admins and organization owners: Default setting. Restricting OKR creation permissions to only the organization administrators and owners is a safe option as you're able to maintain a structured OKR planning and creation workflow.
- Specific people (along with organization admins & organization owners): This option is valuable when you want to have a structured OKR planning & creation workflow and assign to specific people to take ownership of it.
Note
Organization admins and organization owners will always have access to create organizational OKRs or Initiatives by default.
Create permissions for an organization
- Navigate to the organization’s OKRs page.
- Select the Settings tab that you find at the top of the page.
- Under Who can create organization OKRs or Initiatives?, select the preferred option and select Save.
Manage “create permissions” for organizations
Admins can view and revoke access of OKR creation permissions at any time by the following steps:
- Navigate to the organization’s Settings tab.
- Select Manage Access under Who can create organization OKRs or Initiatives? Admins can view all the users who have create permissions access.
- Select X to remove the name(s) of the user(s) you want to revoke the access for.
- Select Save.
Note
By default, for all newly created organizations, the default permission setting for Create permissions on organizational OKRs/Initiatives would be ‘Organization admins and organization owners’. The default permission setting can be changed, but organization admins and owners will still maintain access.
Create permissions for teams
Admins can set Create permissions at the team level to control who can create OKRs and initiatives for the team.
Similar to organization-level settings, admins have three options to choose from:
- Anyone in the organization: Choose this option if the organization is small and cross-functional, where every user contributes to every team in the organization.
- Team admins and Team owners: Restricting OKR creation permissions to only the team administrators and owners is the default option as admins can maintain a structured OKR planning & creation workflow process.
- Specific people (along with team admins & team owners): This option helps admins keep a structured OKR planning and creation workflow and assign specific people ownership of the process such as:
- All members of this team (This would give access to all the users who are members of this team)
- Custom (This option provides you with the capability to search for users within this organization and grant create permissions access to these users)
Note
Permission options may be edited, but team admins and Team owners will always have access to create OKRs or Initiatives irrespective of the option selected. Additionally, organization admins and organization owners will maintain access to create OKRs or initiatives for all teams within the organization.
Establish create permission for a team
- Navigate to the specific team you want to set the create permissions for.
- Select the Team settings tab.
- Under Who can create OKRs or Initiatives for this team? select the preferred option.
- Select Save
Note
When a team is created and the parent team has been defined, the sub-team would default to have the parent team’s create permission setting. This setting can be changed by sub-team managers at any time.
Manage create permissions access for teams
Once admins have created permissions for specific users, they can view and revoke their permissions at any time by the following steps:
- Navigate to the team’s Team settings tab.
- Select Manage Access under Who can create OKRs or Initiatives for this team?
- View all the users who have create permissions access.
- Select X against the name(s) of the user(s) to revoke the access and save the setting.
Note
By default, for all the newly created organizations the default permission setting for create permissions on team level OKRs or Initiatives would be ‘Team admins and team owners’. This permission setting can be changed later if needed.
FAQ (Frequently Asked Questions)
Who can set the create permissions for teams?
- Organization admins, organization owner, team admins and team owner would be able to set create permissions for a team
Who can set Create permissions for an organization?
- Organization owner and organization admin can set create permissions for organizational level OKRs or Initiatives.
Can admins manage access for users when you select Anyone in the organization?
- No, you can only manage access for users when you’ve selected the Specific people(along with team admins & team owners) option.
What is the default permission setting when an organization is created?
- Organizational level OKRs or Initiatives: Only organization admin and organization owner.
- Team level OKRs or Initiatives: Only team admins and team owners.
- Both the options can be changed later if needed.
Does create permissions apply for OKRs and Initiatives at a team and organizational level?
- Yes, create permissions at an organizational level and team level applies to OKRs and Initiatives pertaining to that entity.
Can organization admins or team admins access to create OKRs be removed?
- No, these users would always have access to create OKRs.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for