🔐 Understanding Permissions and Roles in Ops Execution

Permission Comparison Table

Use this table to quickly compare what each permission level can do:

Understanding Permissions

Permissions (also called Privileges) determine what each user can access and do within Ops Execution. Think of them as permission levels - each level has different capabilities and access to different parts of the platform.

There are four permission levels in Ops Execution:

Submitter

• Access to mobile application
• Ability to complete tasks in mobile application 
• Ability to create, edit and archive tasks created by submitter 
• Can access forms that have been distributed by admins to their account in the "My forms" section of the Ops Execution mobile app
• Comment notifications are available via the mobile device only
• Can leave and respond to comments for/from their managers and anyone else above in their hierarchy as long as they are in their team
• Can only delete their own comments

Manager

A manager can do everything that a Submitter can do, plus:

• Create tasks and non-recurring projects in the mobile app or on the Ops Execution web app (managers can edit/delete/archive their own tasks or projects on the Ops Execution web app)
• View tasks assigned by team in mobile app
• View tasks assigned by location in mobile app
• Access to ops-execution.crunchtime.com web app for report viewing/analysis and task creation
• Create workflows (Triggered Alerts and Follow up tasks) from Ops Execution web app
• Create scheduled and non-scheduled reports from the Ops Execution web app
• View/edit/delete user submissions from the Ops Execution web app, if permitted via the form
• Can mention their locations and anyone else above in their hierarchy as long as they are in their team in comments 
• Can delete their own comments
• Comment notifications are available via Web-App and Mobile Device  
• Comment notifications cannot be deleted in the Web-App or Mobile Device, only the red dot alerting of a new notification will NO LONGER show up once read or marked as read. 

Admin

• Access mobile application
• Access ops-execution.crunchtime.com web app for report viewing/analysis and task creation
• Ability to complete tasks
• Can create/archive tasks and recurring/non-recurring projects
• Access forms that have been distributed by admins to their account in the "My forms" section of the Ops Execution mobile app
• View tasks assigned by team in mobile app
• View tasks assigned by location in mobile app
• Create workflows (Triggered Alerts and Follow-up tasks) from Ops Execution web app
• Create scheduled and non-scheduled reports from Ops Execution web app
• View/edit/delete user submissions from Ops Execution web app
• Add/edit/delete users in Ops Execution account
• Create/edit team hierarchy in Ops Execution account
• Create/edit User Roles in Ops Execution account
• Add/edit/delete locations in Ops Execution account
• Create/edit/archive/distribute forms in Ops Execution account
• Can delete their own comments
• Can view comments by going to the location's submissions or tasks
• Comment notifications are available via the Web-App and Mobile Device 
• Comment and/or announcement notifications cannot be deleted in the Web-App or Mobile Device, only the red dot alerting of a new notification will NO LONGER show up once read or marked as read. 

Owner

An Owner can do everything an Admin can, plus:

• Can manage their credit card billing information
• Can manage their Dropbox integration
• Can manage and set the temperature (i.e. °C/°F) for the entire company
• Can add/manage the company logo
• Can choose dissolvable or low adhesive for Crunchtime Labels
• Can update the timezone for the entire company
• Multiple aspects of Ops Execution will by default be directed to the owner of the company's name:
  • Project Creation
  • Forms submitted to be created by Ops Execution
  • User Invites
  • If there is no user in a role and forms are being distributed to the role, it will automatically go to the owner of the company

Understanding Roles

While Permissions determine what a user can do in Ops Execution, Roles define their position in your organizational hierarchy. Using Roles within Ops Execution allows your account to best reflect the actual structure of your organization and is necessary for assigning tasks in bulk through projects.

For example, you might have Roles like "Store Manager," "District Manager," or "Regional Director" - and each of these roles could have users with different Permission levels (Admin, Manager, etc.) depending on their responsibilities.

How to Create Roles

Before you can start dividing users into different roles, you will need to create and label their various roles. To do so, please do the following:

Select the 'Hierarchy' tab from the main navigation.
Navigate to and select the 'Roles' tab.
On the top right corner of the page, select 'Create Role'.
Add in the name of the role, select the Default Permission and the role this position Reports to from the drop-down menus.
Click 'Save'.

You will then be taken back to the Hierarchy screen where you can see your recently created role and its reporting structure.