Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page

Table of Contents
exclude(Request support|Super admin|Admin|User|Users with Company OKR permissions)

Request support👨‍💻


Introduction

A role is a collection of permissions defined for the whole system that you can assign to specific user/s in specific context/s. The combination of roles and context defines specific user's ability to take actions on something.

UpRaise roles & permissions can be managed by UpRaise admins by default. Navigate to ‘Company directory >> Roles & permissions tab’.

Roles & permissions tab contains the list of all permissions that can be given to different users based on their role in UpRaise. Read https://amoeboids.atlassian.net/wiki/spaces/UD/pages/2468741141/Basic+company+directory+attributes#Role for more details.

Click on each section to define your roles & permissions set up for each module of UpRaise.

Columns are defined based on UpRaise roles. Admin, Super admin & No access roles are set by default whereas for User with Company OKR permissions & User role, permissions can be modified by admins or users with sufficient permissions.

Excerpt

UpRaise roles

Currently, there are 4 types of roles in UpRaise.

Table of Contents
minLevel3
absoluteUrltrue

Super admin

This user will have 'god-like' view to the entire data in the app. They can manage all administrative features and make any changes in the UpRaise setup. They have complete visibility of the data within the app regardless of it is shared with them or not.

Admin

This is the secondary level administrative role. Users with this role can manage all administrative features. However, in terms of data visibility, they can view/edit all the data they have created and that is explicitly shared with them. For example, admins can view company OKRs, team OKRs that are created by themselves or are explicitly shared with them. Same is the case for form templates & distributions.

User

Users with this role are non-administrative users. By default, these users would have access to non-admin features of UpRaise. They can view data that is created by themselves & that is shared explicitly with them. However, these users can be given admin/super admin like permissions from Roles & permissions tab of Company directory.

Users with Company OKR permissions

This user role is specially created for managing company OKRs. This user has similar permissions that are given to user role. Along with that, they have default permission of managing UpRaise company OKRs. these users can also be given admin/super admin like permissions from Roles & permissions tab of Company directory.

Editing permissions for each UpRaise role

Roles & permission page contains a section-wise list of actions for each of UpRaise features. One can manage permissions for these actions by clicking on edit/pencil icon. Note that, on mouseover, one can edit permissions only for 'Users & Users with company OKRs permissions'.

What permissions can be managed from Roles & permissions page?

  • Direct manager - Manager assigned to a user within company directory.

    • Example - is B’s manager.

  • Indirect manager - Manager of user’s manager.

    • Example - C is A’s manager, C is B’s indirect manager.

  • Team lead - User selected as team lead.

    • Example - X is team 1’s team lead.

  • Indirect team lead - Team lead of the parent team.

    • Example -Team 2 is Team 1’s parent team. Y is team 2’s team lead. So Y is an indirect team lead.

Expand
titleOKRs - Generic permissions

Permissions

Possible value

Description

OKR settings/administration

  • Yes

  • If yes, user with given role can manage OKR settings.

  • No

  • If no, user with given role cannot manage OKR settings

Create comment

  • Yes

  • If yes, user with given role can create comments within OKRs

  • No

  • If yes, user with given role cannot create comments within OKRs

Edit comment

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can edit comments within OKRs always regardless of who has created comments.

    • If when creator, user with given roles can edit comments only that are created by thmeselves as logged in user.

  • No

  • If No, user with given role cannot edit any comments within OKRs.

Delete comment

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can delete comments within OKRs always regardless of who has created comments.

    • If when creator, user with given roles can delete comments only that are created by themselves as logged in user.

  • No

  • If No, user with given role cannot delete any comments within OKRs.

Create attachment

  • Yes

  • If yes, user with given role can attach files within OKRs.

  • No

  • If yes, user with given role cannot attach files within OKRs.

Delete attachment

  • Yes

    • When Creator

    • Always

  • Yes-

    • If When creator, user with given role can delete attached within own OKRs.

    • If always, user with given role can delete all attached files within all OKRs.

  • No

  • If yes, user with given role cannot delete attached files within OKRs.

Manage key result reminders

  • Yes

    • Always

    • When owner of key result

  • Yes -

    • If always, user with given role can manage KR reminders for all users regardless of who owns the KR.

    • If when owner of key result, user with given roles can manage KR reminders only for own KRs.

  • No

  • If No, user with given role cannot manage any KR reminders.

Objective edit grades

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can edit all OKR grades for all objectives regardless of who owns the objectivehas added it.

    • If when creator, user with given roles role can edit grades only for own objectivesif they have added it.

  • No

  • If No, user with given role cannot edit any grades of any objectives.

Expand
titleOKRs - Company level

Permissions

Possible value

Description

Create company objective

  • Yes

  • If yes, user with given role can create company objectives.

  • No

  • If no, user with given role cannot create company objectives.

View company objective

  • Yes

    • Always

    • When creator

    • When owner

    • When shared

  • Yes -

    • If always, user with given role can always view all company objectives no matter who creats/owns them.

    • If when creator, user with given role can view company objectives they have created.

    • If when owner, user with given roles can view company objectives they own.

    • If when shared, user with given role can view company objectives that are shared by other users.

  • No

  • If no, user with given role cannot view company objectives.

Edit company objective

  • Yes

    • Always

    • When creator

    • When owner

  • Yes -

    • If always, user with given role can edit all company objectives regardless of who created/owns them.

    • If when creator, user with given role can edit company objectives they have created.

    • If when owner, user with given role can edit company objectives they own.

  • No

  • If no, user with given role cannot edit any company objectives.

Delete company objective

  • Yes

    • Always

    • When creator

    • When owner

  • Yes -

    • If always, user with given role can delete all company objectives regardless of who has created/owns them.

    • If when creator, user with given role can delete company objectives they have created.

    • If when owner, user with given role can delete company objectives they own.

  • No

  • If no, user with given role cannot delete any company objectives .

Punch-in company objective

  • Yes

    • Always

    • When creator

    • When owner

  • Yes -

    • If always, user with given role can punch-in on all company objectives regardless of who has created/owns them.

    • If when creator, user with given role can punch -in on company objectives they have created.

    • If when owner, user with given role can puch-in company objectives they own.

  • No

  • If no, user with given role cannot punch-in on any company objectives.

Reopen company objective

  • Yes

    • Always

    • When creator

    • When owner

  • Yes -

    • If always, user with given role can reopen all closed company objectives regardless of who has created/owns them.

    • If when creator, user with given role can reopen closed company objectives they have created.

    • If when owner, user with given role can reopen closed company objectives they own.

  • No

  • If no, user with given role cannot reopen any closed company objectives.

Add company objective grades

  • Yes

    • Always

    • When creator

    • When owner

  • Yes -

    • If always, user with given role can add grades for closed company objectives regardless of who has created/owns them.

    • If when creator, user with given role can add grades for closed company objectives they have created.

    • If when owner, user with given role can add grades for closed company objectives they own.

  • No

  • If no, user with given role cannot add grades for any closed objectives at company level.

Abandon/close without grading/close & carry forward company objective

  • Yes

    • Always

    • When creator

    • When owner

Yes -

  • If always, user with given role can Abandon/close without grading/close & carry forward all company level objectives regardless of who has created/owns them.

  • If when creator, user with given role can Abandon/close without grading/close & carry forward all company level objectives they have created.

  • If when owner, user with given role can Abandon/close without grading/close & carry forward all company level objectives they own.

  • No

  • If no, user with given role cannot Abandon/close without grading/close & carry forward any

Create company key result

  • Yes

    • Always

    • When creator of parent objective

    • When owner of parent objective

Yes -

  • If always, user with given role can create KRs for all company objectives regardless of who has created an objective/who owns it.

  • If when creator of parent objective, user with given role can create KRs for company objectives they have created.

  • If when owner of parent objective, user with given role can create KRs for company objectives they own.

  • No

  • If no, user with given role cannot create KRs for any company objective.

Edit company key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

Yes -

  • If always, user with given role can edit all KRs from all company objectives regardless of who has created/owns objective

  • If when creator, user with given role can edit KRs they have created within company objective/s.

  • If when owner, user with given role can edit KRs they own in company objective/s.

  • If when creator of parent objective, user with given role can edit KRs for parent company objectives they have created.

  • If when owner of parent objective, user with given role can edit KRs for parent company objectives they own.

  • No

  • If no, user with given role cannot edit KRs for any company objective.

Delete company key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

Yes -

  • If always, user with given role can delete all KRs from all company objectives regardless of who has created/owns objective

  • If when creator, user with given role can delete KRs they have created within company objective/s.

  • If when owner, user with given role can delete KRs they own company objective/s.

  • If when creator of parent objective, user with given role can delete KRs from parent company objectives they have created.

  • If when owner of parent objective, user with given role can delete KRs from parent company objectives they own.

  • No

  • If no, user with given role cannot delete KRs from any company objective.

Punch-in company key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

Yes -

  • If always, user with given role can punch-in all KRs from all company objectives regardless of who has created/owns objectives.

  • If when creator, user with given role can punch-in KRs they have created within company objective/s.

  • If when owner, user with given role can punch-in KRs they own within company objective/s.

  • If when creator of parent objective, user with given role can punch-in KRs from parent company objectives they have created.

  • If when owner of parent objective, user with given role can punch-in KRs from parent company objectives they own.

  • No

  • If no, user with given role cannot punch-in KRs from any company objective.

Add/Delete company key result action

  • Yes

    • Always

    • When creator of key result

    • When owner of key result

    • When creator of parent objective

    • When owner of parent objective

Yes -

  • If always, user with given role can add/delete KR actions to all KRs from all company objectives regardless of who has created/owns objective

  • If when creator, user with given role can add/delete KR actions of KRs they have created within company objectives/s.

  • If when owner, user with given role can add/delete KR actions of KRs they own within company objectives/s.

  • If when creator of parent objective, user with given role can add/delete KR actions to KRs from parent company objectives they have created.

  • If when owner of parent objective, user with given role can add/delete KR actions to KRs from parent company objectives they own.

  • If no, user with given role cannot add/delete KR actions to KRs from any company objective.

Expand
titleOKRs - Team level

Permissions

Possible value

Description

Create team

  • Yes

    • Always

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If always, user with given role can create team objectives for any team within UpRaise.

    • If when team member, user with given role can create team objectives only for his team only if he is a team lead.

    • If when team member, user with given role can create team objectives as team member for team/s they belong to

    • If when indirect team lead, user with given role can create team objective for child team/s as indirect team lead (team lead of parent team)

  • No

  • If no, user with given role cannot create team objective for any team in UpRaise

View team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

    • When shared

  • Yes -

    • If always, user with given role can view any team objective.

    • If when creator, user with given role can view team objectives they have created.

    • If when owner, user with given role can view team objectives they own

    • If when team lead, user with given role can view team objectives of team/s they are team lead of

    • If when team member, user with given role can view team objectives of team/s they belong to

    • If when indirect team lead, user with given role can view team objectives of team/s they are indirect team leads of(indirect team lead is a team lead of your parent team)

  • No

  • If no, user with given role cannot view any team objective

Edit team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If always, user with given role can edit all team objectives.

    • If when creator, user with given role can edit team objectives that they have created

    • If when owner, user with given role can edit team objectives they own

    • If when team lead, user with given role can edit team objectives of team/s they are team lead of

    • If when team member, user with given role can edit team objectives of team/s they belong to

    • If when indirect team lead, user with given role can edit team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team)

  • No

  • If no, user with given role cannot edit any team objectives

Delete team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If always, user with given role can delete all team objectives.

    • If when creator, user with given role can delete team objectives that they have created

    • If when owner, user with given role can delete team objectives they own

    • If when team lead, user with given role can delete team objectives of team/s they are team lead of

    • If when team member, user with given role can delete team objectives of team/s they belong to

    • If when indirect team lead, user with given role can delete team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team)

  • No

  • If no, user with given role cannot delete any team objectives

Punch-in team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If always, user with given role can punch-in all team objectives.

    • If when creator, user with given role can punch-in team objectives that they have created

    • If when owner, user with given role can punch-in team objectives they own

    • If when team lead, user with given role can punch-in team objectives of team/s they are team lead of

    • If when team member, user with given role can punch-in team objectives of team/s they belong to

    • If when indirect team lead, user with given role can punch-in team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team)

  • No

  • If no, user with given role cannot punch-in any team objectives

Reopen team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If always, user with given role can reopen all closed team objectives.

    • If when creator, user with given role can reopen closed team objectives that they have created.

    • If when owner, user with given role can reopen closed team objectives they own.

    • If when team lead, user with given role can reopen closed team objectives of team/s they are team lead of.

    • If when team member, user with given role can reopen closed team objectives of team/s they belong to.

    • If when indirect team lead, user with given can reopen closed team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team).

  • No

  • If no, user with given role cannot reopen any team objectives

Add team objective grades

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

Yes -

  • If always, user with given role can add grades to all ready for grading team objectives.

  • If when creator, user with given role can add grades to ready for grading team objectives that they have created.

  • If when owner, user with given role can add grades to ready for grading team objectives they own.

  • If when team lead, user with given role can add grades to ready for grading team objectives of team/s they are team lead of.

  • If when team member, user with given role can add grades to ready for grading team objectives of team/s they belong to.

  • If when indirect team lead, user with given role can add grades to ready for grading team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team).

  • No

  • If no, user with given role cannot add grades to ready for grading team objectives.

Abandon/close without grading/close & carry forward team objective

  • Yes

    • Always

    • When creator

    • When owner

    • When team lead

    • When team member

    • When indirect team lead

Yes -

  • If always, user with given role can Abandon/close without grading/close & carry forward team objective.

  • If when creator, user with given role can Abandon/close without grading/close & carry forward team objectives that they have created.

  • If when owner, user with given role can Abandon/close without grading/close & carry forward team objectives they own.

  • If when team lead, user with given role can Abandon/close without grading/close & carry forward team objectives of team/s they are team lead of.

  • If when team member, user with given role can Abandon/close without grading/close & carry forward team objectives of team/s they belong to.

  • If when indirect team lead, user with given role can Abandon/close without grading/close & carry forward team objectives of team/s they are indirect team leads of (indirect team is a team lead of your parent team).

  • No

  • If no, user with given role cannot Abandon/close without grading/close & carry forward team objectives.

Create team key result

  • Yes

    • Always

    • When creator of parent objective

    • When owner of parent objective

    • When team lead of parent objective

    • When team member of parent objective

    • When indirect team lead of parent objective

  • Yes -

    • If always, user with given role can create key results in any team objective.

    • If when creator of parent objective, user with given role can add key results as creator of the parent (the objective to which KR belongs to) team objective

    • If when owner of the parent objective, user with given role can add key results as owner of parent (the objective to which KR belongs to) team objective

    • If when team member of parent objectives, user with given role can create key results as team member of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when indirect team lead of parent objectives, the user with given role can create key results as team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

  • No

  • If no, user with given role cannot create key results in any team objective.

Edit team key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

    • When team lead of parent objective

    • When team member of parent objective

    • When indirect team lead of parent objective

  • Yes -

    • If always, user with given role can edit key results in any team objective.

    • If when creator, user with given role can edit key results they have created.

    • If when owner, user with given role can edit key results from the team objectives they own.

    • If when creator of parent objective, user with given role can edit key results from the team objectives they have created.

    • If when owner of the parent objective, user with given role can edit key results as owner of parent (the objective to which KR belongs to) team objective

    • If when team lead of parent objectives, the user with given role can edit key results as team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when team member of parent objectives, user with given role can edit key results as team member of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when indirect team lead of parent objectives, the user with given role can edit key results as indirect team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

  • No

  • If no, user with given role cannot edit key results in any team objective.

Delete team key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

    • When team lead of parent objective

    • When team member of parent objective

    • When indirect team lead of parent objective

  • Yes -

    • If always, user with given role can delete key results in any team objective.

    • If when creator, user with given role can delete KR as creator of KR from for team objective

    • If when owner, user with given role can edit KR for team objectives they ow

    • If always, user with given role can delete key results in any team objective.

    • If when creator of parent objective, user with given role can delete key results as creator of the parent (the objective to which KR belongs to) team objective

    • If when owner of the parent objective, user with given role can delete key results as owner of parent (the objective to which KR belongs to) team objective

    • If when team member of parent objectives, user with given role can delete key results as team member of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when indirect team lead of parent objectives, the user with given role can delete key results as team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

  • No

  • If no, user with given role cannot delete key results in any team objective.

Punch-in team key result

  • Yes

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

    • When team lead of parent objective

    • When team member of parent objective

    • When indirect team lead of parent objective

  • Yes -

    • If always, user with given role can punch-in key results in any team objective.

    • If when creator, user with given role can punch-in KR as creator of KR from for team objective

    • If when owner, user with given role can punch-in KR for team objectives they own

    • If when creator of parent objective, user with given role can punch-in key results as creator of the parent (the objective to which KR belongs to) team objective

    • If when owner of the parent objective, user with given role can punch-in key results as owner of parent (the objective to which KR belongs to) team objective

    • If when team lead of parent objectives, the user with given role can punch-in key results as team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when team member of parent objectives, user with given role can delete key results as team member of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when indirect team lead of parent objectives, the user with given role can delete key results as indirect team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

  • No

  • If no, user with given role cannot punch-in key results in any team objective.

Add/Delete team key result action

  • Yes

    • Always

    • When creator of key result

    • When owner of key result

    • When creator of parent objective

    • When owner of parent objective

    • When team lead of parent objective

    • When team member of parent objective

    • When indirect team lead of parent objective

  • Yes -

    • If always, user with given role can Add/Delete team key result action in any team objective.

    • If when creator, user with given role can Add/Delete team key result action as creator of KR from for team objective

    • If when owner, user with given role can Add/Delete team key result action for team objectives they ow

    • If when creator of parent objective, user with given role can Add/Delete team key result action as creator of the parent (the objective to which KR belongs to) team objective

    • If when owner of the parent objective, user with given role can Add/Delete team key result action as owner of parent (the objective to which KR belongs to) team objective

    • If when team lead of parent objectives, the user with given role can Add/Delete team key result action as team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when team member of parent objectives, user with given role can Add/Delete team key result action as team member of the team to which parent (the objective to which KR belongs to) objective belongs to

    • If when indirect team lead of parent objectives, the user with given role can Add/Delete team key result action as indirect team lead of the team to which parent (the objective to which KR belongs to) objective belongs to

  • No

  • If no, user with given role cannot Add/Delete team key result action in any team objective.

Expand
titleOKRs - Individual level

Permissions

Possible value

Description

Create individual objective

  • Yes -

    • Always

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes

    • If always, user with given role can create individual objectives for anyone.

    • If when owner, user with given role can create individual objective for themselves.

    • If when manager of owner, user with role can create individual objective for their direct reports.

    • If when indirect manager of owner, user with role can create individual objective for their direct reporting manager’s direct report.

  • No

  • If no, user with given role cannot create individual objectives for anyone.

View individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

    • When shared

  • Yes

    • If always, user with given role can view all individual objectives.

    • If when creator, user with given role can view individual objective they have created.

    • If when owner, user with given roles can view individual objectives they own.

    • If when manager of owner, user with role can view individual objective for their direct reports own.

    • If when indirect manager of owner, user with role can view individual objective owned by direct reporting manager’s direct report.

    • If when shared, user with given role can view individual objectives when they are shared explicitly.

  • No

  • If no, user with given role cannot view any individual objective.

Edit individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes

    • If always, user with given role can edit all individual objectives.

    • If when creator, user with given role can edit individual objective they have created.

    • If when owner, user with given role can edit individual objective they own.

    • If when manager of owner, user with role can edit individual objective for their direct reports own.

    • If when indirect manager of owner, user with role can edit individual objective owned by direct reporting manager’s direct report.

  • No

  • If no, user with given role cannot edit any individual objective.

Delete individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes

    • If always, user with given role can delete all individual objectives.

    • If when creator, user with given role can delete individual objective they have created.

    • If when owner, user with given role can delete individual objective they own.

    • If when manager of owner, user with role can delete individual objective for their direct reports own.

    • If when indirect manager of owner, user with role can delete individual objective owned by direct reporting manager’s direct report.

  • No

  • If no, user with given role cannot delete any individual objective.

Punch-in individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes -

    • If always, user with given role can punch-in all individual objectives.

    • When creator, user with given role can punch-in on individual objective they have created.

    • When owner, user with given role can punch-in on individual objective they own.

    • When manager of owner, user with given role can punch-in on individual objective owned ny their direct reports.

    • When indirect manager of owner, user with given role can punch-in on individual objective owned by their direct report’s direct report.

  • No

  • If no, user with given role cannot punch-in on any individual objective.

Reopen individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes -

    • If always, user with given role can reopen all individual objectives.

    • When creator, user with given role can reopen individual objective they have created.

    • When owner, user with given role can reopen individual objective they own.

    • When manager of owner, user with given role can reopen individual objective owned by their direct reports.

    • When indirect manager of owner, user with given role can reopen individual objective owned by their direct report’s direct report

  • No

  • If no, user with given role cannot reopen any individual objective.

Add individual objective grades

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes -

    • If always, user with given role can add grades on all ready for grading individual objectives.

    • When creator, user with given role can add grades on ready for grading individual objective they have created.

    • When owner, user with given role can add grades on ready for grading individual objective they own.

    • When manager of owner, user with given role can add grades on ready for grading individual objective owned ny their direct reports.

    • When indirect manager of owner, user with given role can add grades on ready for grading individual objective owned by their direct report’s direct report.

  • No

  • If no, user with given role cannot add grades on any ready for grading individual objective.

Abandon/close without grading/close & carry forward individual objective

  • Yes -

    • Always

    • When creator

    • When owner

    • When manager of owner

    • When indirect manager of owner

  • Yes -

    • If always, user with given role can Abandon/close without grading/close & carry forward individual objectives.

    • When creator, user with given role can Abandon/close without grading/close & carry forward individual objective they have created.

    • When owner, user with given role can Abandon/close without grading/close & carry forward individual objective they own.

    • When manager of owner, user with given role can Abandon/close without grading/close & carry forward individual objective owned by their direct reports.

    • When indirect manager of owner, user with given role can Abandon/close without grading/close & carry forward individual objective owned by their direct report’s direct report.

  • No

  • If no, user with given role cannot Abandon/close without grading/close & carry forward any individual objective.

Create individual key result

  • Yes -

    • Always

    • When creator of parent objective

    • When owner of parent objective

    • When manager of parent objective owner

    • When indirect manager of parent objective owner

  • Yes -

    • If always, user with given role can create key result within individual objectives.

    • If when creator of the parent objective, user with given role can create KRs within individual objective they have created.

    • If manager of parent objective owner, user with given role can create KRs within individual objective as manager of individual objective owner.

    • If when indirect manager of parent objective owner, user with given role can create KRs within individual objective owned by their direct report’s direct report.

  • No

  • If no, user with given role cannot create key result within individual objectives.

Delete individual key result

  • Yes -

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

    • When manager of parent objective owner

    • When indirect manager of parent objective owner

  • Yes -

    • If always, user with given role can delete key result within individual objectives.

    • If when creator of KR, user with given role can delete key result within individual objectives.

    • If when owner of KR, user with given role can delete key result within individual objectives.

    • If when creator of parent objective, user with given role can delete key result within individual objectives they have created.

    • If when owner of parent objective, user with given role can delete key result within individual objectives they own.

    • If when manager of parent objective owner, user with given role can delete key result as manager of individual objective owner.

    • If when indirect manager of parent objective owner, user with given role can delete key result as indirect manager of individual objective owner.

  • No

  • If no, user with given role cannot delete key result within any individual objective.

Punch-in individual key result

  • Yes -

    • Always

    • When creator

    • When owner

    • When creator of parent objective

    • When owner of parent objective

    • When manager of parent objective owner

    • When indirect manager of parent objective owner

  • Yes -

    • If always, user with given role can punch-in key result within individual objectives.

    • If when creator of KR, user with given role can punch-in key result within individual objectives.

    • If when owner of KR, user with given role can punch-in key result within individual objectives.

    • If when creator of parent objective, user with given role can punch-in key result within individual objectives they have created.

    • If when owner of parent objective, user with given role punch-in key result within individual objectives they own.

    • If when manager of parent objective owner, user with given role can punch-in key result as manager of individual objective owner.

    • If when indirect manager of parent objective owner, user with given role can punch-in key result as indirect manager of individual objective owner.

  • No

  • If no, user with given role cannot punch-in key result within any individual objective.

Add/Delete individual key result action

  • Yes -

    • Always

    • When creator of key result

    • When owner of key result

    • When creator of parent objective

    • When owner of parent objective

    • When manager of parent objective owner

    • When indirect manager of parent objective owner

  • Yes -

    • If always, user with given role can create or delete KR actions for KRs within any individual objective.

    • If when creator of key result, user with given role can create or delete KR actions for KRs they have created within any individual objective.

    • If when owner of key result, user with given role can create or delete KR actions for KRs they own within individual objective.

    • If when creator of parent objective, user with given role can create or delete KR actions for KRs if they are creator of parent individual objective.

    • If when owner of parent objective, user with given role can create or delete KR actions for KRs if they own parent individual objective.

    • If when manager of parent objective owner, user with given role can create or delete KR actions for KRs if they are manager of parent individual objective’s owner to which.

    • If when indirect manager of parent objective owner, user with given role can create or delete KR actions if they are indirect manager of parent individual objective’s owner.

  • No

If no, user with given role can create or delete KR actions for KRs within any individual objective.

Expand
titleFeedback - Generic

Permissions

Possible value

Description

Show feedback menu

  • Yes

  • No

  • If yes, feedback menu is shown to user with given role.

  • If no, feedback menu is hidden from user with given role.

Feedback settings/administration

  • Yes

  • No

  • If yes, user with given role can manager feedback settings/administration.

  • If no, user with given role cannot manager feedback settings/administration.

Expand
titleFeedback - Feedback

Permissions

Possible value

Description

Give feedback

  • Yes

    • For any user

    • For direct manager

    • For direct reports

    • For indirect manager

    • For indirect reports

    • For team members

  • Yes

    • If for any user, user with given role can give feedback to any user.

    • If for direct manager, user with given role can give feedback to their direct manager.

    • If for direct reports, user with given role can give feedback to their direct reports

    • If for indirect manager, user with given role can give feedback to their indirect manager (here, manager’s manager).

    • If for indirect reports, user with given role can give feedback to their indirect reports(here, direct report’s direct report)

    • For team members, user with given role can give feedback to their team members.

  • No

  • If no, user with given role cannot give feedback to any user.

View feedback

  • Yes

    • Always

    • When creator

    • When shared

  • Yes -

    • If always, user with given role can view any feedback in the system.

    • If when creator, user with give role can view feedback that they have created.

    • If when shared, user with given role can view feedback those are made visible to them.

  • No

  • If no, user with given role cannot view any feedback.

Edit feedback

  • Yes

    • Always

    • When creator

    • When shared

  • Yes -

    • If always, user with given role can edit any feedback in the system.

    • If when creator, user with give role can edit feedback that they have created.

    • If when shared, user with given role can edit feedback those are made visible to them.

  • No

  • If no, user with given role cannot edit any feedback.

Edit feedback visibility

  • Yes

    • Always

    • When creator

    • When receiver

    • When shared

  • Yes -

    • If always, user with given role can edit visibility of any feedback in the system.

    • If when creator, user with give role can edit visibility of feedback that they have created.

    • If when creator, user with give role can edit visibility of feedback that they have received.

    • If when shared, user with given role can edit visibility feedback those are made visible to them.

  • No

  • If no, user with given role cannot edit visibility of any feedback.

Delete feedback

  • Yes

    • Always

    • When creator

    • When shared

  • Yes -

    • If always, user with given role can delete any feedback in the system.

    • If when creator, user with give role can delete feedback that they have created.

    • If when shared, user with given role can delete feedback those are made visible to them.

  • No

  • If no, user with given role cannot delete any feedback.

Expand
titleFeedback - Feedback requests

Permissions

Possible value

Description

Request feedback

  • Yes

    • For any user

    • For self

    • For direct reports

    • For indirect reports

    • For team members

  • Yes

    • If for any user, user with given role can request feedback from any user.

    • If for self, user with given role can request feedback for themselves.

    • If for direct reports, user with given role can request feedback from their direct reports.

    • If for indirect reports, user with given role can request feedback from their indirect reports.

    • If for team members, user with given role can request feedback from their team members.

  • No

If no, user with given role cannot request feedback from any user.

View feedback requests

  • Yes

    • Always

    • When request creator

    • When request receiver

  • Yes

    • If always, user with given role can view any feedback request within the system.

    • If when request creator, user with given role can view feedback requests they have created.

    • If when request receiver, user with given role can view feedback requests they have received.

  • No

  • If no, user with given role cannot view any feedback requests.

Delete feedback requests

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can delete any feedback request within the system.

    • If when creator, user with given role can delete feedback request they have created.

  • No

  • If no, user with given role cannot delete any feedback requests.

Expand
titleForms - Templates

Permissions

Possible value

Description

Create template

  • Yes

  • No

  • If yes, user with given role can create templates.

  • If no, user with given role cannot create templates.

View template

  • Yes

    • Always

    • When creator

    • When default template

  • Yes -

    • If always, user with given role can view all templates.

    • If when creator, user with given role can view templates they have created.

    • If when default template, user with given role can view all default templates.

  • No

  • No, If no, user with given role cannot view any templates.

Edit template

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can edit all templates.

    • If when creator, user with given role can edit templates they have created.

  • No

  • No, If no, user with given role cannot edit any templates.

Delete template

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can delete all templates.

    • If when creator, user with given role can delete templates they have created.

  • No

  • No, If no, user with given role cannot delete any templates.

Expand
titleForms - Distributions

Permissions

Possible value

Description

Create distribution

  • Yes

  • No

  • If yes, user with given role can create distributions.

  • If no, user with given role cannot create distributions.

View distribution

  • Yes

    • Always

    • When creator

    • When default template

  • Yes -

    • If always, user with given role can view all distributions.

    • If when creator, user with given role can view distributions they have created.

    • If when default template, user with given role can view distribution made with default templates.

  • No

  • No, If no, user with given role cannot view any distributions.

View distribution response

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can view all distribution responses.

    • If always, user with given role can view distribution responses for distributions they have created.

  • No

  • If no, user with given role cannot view any distributions.

Delete distribution

  • Yes

    • Always

    • When creator

  • Yes -

    • If always, user with given role can delete any distribution.

    • If always, user with given role can delete distributions they have created.

  • No

  • No, If no, user with given role cannot delete any distributions.

Expand
titleCompany directory - Generic

Permissions

Possible value

Description

Manage roles & permissions

  • Yes

  • No

  • If yes, user with given role can manage UpRaise roles & permissions.

  • If no, user with given role cannot manage UpRaise roles & permissions.

Manage HRMS sync

  • Yes

  • No

  • If yes, user with given role can manage HRMS sync.

  • If no, user with given role cannot manage HRMS sync.

Manage designation

  • Yes

  • No

  • If yes, user with given role can manage UpRaise designations.

  • If no, user with given role cannot manage UpRaise designations.

Expand
titleCompany directory - User management

Permissions

Possible value

Description

Add user/s

  • Yes

  • No

  • If yes, user with given role can add new users with UpRaise.

  • If no, user with given role cannot add new users within UpRaise.

View user/s in company directory

  • Yes

  • No

  • If yes, user with given role can view users/company directory.

  • If no, user with given role cannot view users/company directory.

Edit user/s

  • Yes

    • All

    • Self

    • When direct manager

    • When indirect manager

  • Yes-

    • If all, user with given role can edit all UpRaise users.

    • If self, user with given role can edit own user details only.

    • If when direct manager, user with given rolecan edit users details of their direct reports.

    • If when indirect manager, user with given role can edit users details of their direct report's direct report.

  • No

If no, user with given role cannot edit any user’s details.

Edit user role

  • Yes

  • No

  • If yes, user with given role can edit UpRaise users roles.

  • If no, user with given role cannot edit UpRaise users roles.

Expand
titleCompany directory - Team management

Permissions

Possible value

Description

Create team

  • Yes

  • No

  • If yes, user with given role can create UpRaise teams.

  • If no, user with given role cannot create UpRaise teams.

View team

  • Yes

  • No

  • If yes, user with given role can view UpRaise teams.

  • If no, user with given role cannot view UpRaise teams.

Edit team

  • Yes

    • All

    • When team lead

    • When team member

    • When indirect team lead

  • Yes -

    • If all, user with given role can edit UpRaise teams.

    • If no, user with given role cannot create UpRaise teams.

  • No

  • If no, user with given role cannot create UpRaise teams.

Delete team and make them active/inactive

  • Yes

    • All

    • When team lead

    • When team member

    • When indirect team lead

  • Yes-

    • If all, user with given role can delete team or make them active or inactive.

    • If when team lead, user with given role can delete team & make them active/inactive as team lead.

    • If when team member, user with given role can delete team & make them active/inactive being a team member.

    • If when indirect team lead, user with given role can delete team & make them active/inactive being an indirect team lead.

  • No

  • If no, user with given role cannot delete team & make them active/inactive.

Manage units

  • Yes

  • No

  • If yes, user with given role can manage units

  • If no, user with roles cannot manage units.

Expand
titleReports/Settings - Generic

Permissions

Possible value

Description

View reports

  • Yes

  • No

  • If yes, user with given role can view OKR progress charts and Objective cycle status & compliance report.

  • If no, user with given role cannot view any UpRaise reports.

Manage settings

  • Yes

  • No

  • If yes, user with given role can UpRaise settings.

  • If no, user with given role cannot manage UpRaise settings.


Iframe
scrollingauto
srchttps://amoeboids.typeform.com/c/loItQqk5?typeform-cui-avatar=https://images.typeform.com/images/RsZMyNqkfNcY#url=/spaces/UD/pages/32636964/General+settings
width350
frameborderhide
alignmiddle
height250