Permission sets in Operating
All about permissions and how you may configure them for different users in your company
Written By Matti Parviainen
Last updated About 19 hours ago
Permission sets control what each user can see and do in Operating. This page describes how the permission system works, lists every permission available, and provides guidance on configuring permission sets for common roles.
How permission sets work
Each user in Operating is assigned exactly one permission set. The permission set defines which parts of the application they can access and what actions they can perform.
Key concepts:
Permission sets are defined at the organization level. Admins create and manage them in Settings → Permissions.
Each user gets one permission set. When a user is created, they are assigned the default permission set, which can be changed at any time.
There is a default permission set. One permission set is marked as the default and is automatically assigned to new users when they first log in. Review this carefully — if it's too permissive, every new user gets broad access immediately.
Built-in permission sets are provided as starting points (e.g., Admin, Employee, Manager). You can customize these or create new ones.
The Admin permission set cannot be removed as a profile. You always need at least one admin-level permission set.
A user is not the same as a person. A person can exist in Operating without a user account. A user account is only needed when someone needs to log in. See Give team members access for details.
The concept of ownership in Operating permissions
There are different kinds of owners for Projects. All different owners have access to projects (and the Client Owner has access to all projects for that Client).
The “reports to” manager relation in Operating
In order to handle who should be able to see whose time entries, and for easy filtering of “all of my people”, we provide the option to add a “reports to” field for each person. When the Reporting structure feature is in use, any Person may have a manager’s name set in their profile under “Reports to”.
In order to prevent problems with permission limitations, we have decided that a person will always see the people who report to them. The manager will also see all of the things that the person who reports to them sees. In order for a supervising manager to do their job, they need to see what their people are up to. Please reach out to support@operating.app if you have questions related to this logic.
The concept of membership in Operating permissions

For some permission settings, you can choose to allow things based on project membership.
When a user is added to a project team setup (named to work in a position), they gain membership in it and can see all other people on the project. Project owners, secondary owners, client owners and invoice owners will also have access to the projects under their management.
Permission reference
The permissions screen is organized into eight sections. Each section is described below with all available permissions and their options.
Features
Feature toggles control access to major areas of the Operating UI. Each can be turned on or off independently.
People
Controls visibility and management of person records.
Projects and Clients
Controls what project and client data the user can access and modify.
Note: even when a user can see a project, the financial details they see depend on the Financials permissions below. Project visibility and financial visibility are separate controls.
Allocations and Positions
Controls the ability to create and manage staffing data.
Time entries
Controls time tracking visibility and management.
Financials
Controls visibility and management of monetary data — rates, costs, revenue, invoicing, and expenses.
Notes
Administration
Controls access to organization-wide configuration. These permissions are typically reserved for admins and operations staff.
Common permission set patterns
The built-in permission sets (Admin, Employee, Manager) provide a starting point. Here's how to think about configuring sets for typical consulting roles:
Consultants (time tracking focus): Enable Hours and Timeline features. Set "Edit own" for time entries. Scope project and people visibility to what they're involved with. Disable financial visibility unless your organization shares margin data broadly. Disable all Administration permissions.
Project managers: Enable most features. Give project and allocation management for their projects. Enable revenue visibility. Consider whether they need cost visibility for margin decisions. Enable Edit approvals if they approve timesheets.
Staffing managers: Enable Timeline, Directory, Projects, People, and Positions features. Give full allocation and position management with "See all" for people and projects. Revenue visibility helps them understand rate implications when staffing.
Finance / invoicing team: Enable broad financial permissions — cost visibility, revenue visibility, invoice visibility, expense management. Give time entry visibility (needed to verify entries before invoicing). Disable allocation and position management unless they also staff projects.
External contractors: Minimal permissions. Enable Hours for time tracking. Scope everything to only their own projects and entries. Disable financial visibility, administration, and broad people/project visibility.
Executives (read-only oversight): Enable Reports, Projects, People, and Client features. Enable cost and revenue visibility. Disable all create/edit/delete and Administration permissions.
Data sensitivity considerations
Cost rates are derived from salaries. Broad cost visibility lets people infer compensation information.
Revenue visibility reveals client billing rates. Less sensitive than costs, but still commercially sensitive.
Manage permission sets is the most powerful admin permission — it enables self-escalation of access.
Import CSV files can create or modify data in bulk. Restrict to trusted admins.
Manage cards controls user account management — who can invite or remove users.
Related articles
How to structure permissions to match your company culture – because tools have a way of strengthening or weakening your culture
Give team members access — creating user accounts and assigning permission sets
SSO: Entra ID — configuring single sign-on
How to add a new person — adding people and configuring their access