Skip to main content

Dependent Permissions in Custom Permission Sets

Some permissions only work together with others. When you turn one on or off in a custom permission set, its dependent permissions follow.

When you build a custom permission set, some permissions depend on others. Turning one on or off also turns on or off the permissions it depends on, or that depend on it.

Custom permission sets are available on the Ultimate subscription plan.

How It Works

Example: turning on View tasks also turns on View projects where the user is a member, because you can’t see tasks without seeing their project. Turning off View projects where the user is a member also turns off View tasks.

Before anything changes, Productive tells you the permission has dependencies and how many other permissions will change. Click Turn on or Turn off to confirm.

Common Dependencies

Turning on

Also turns on

Add, edit, and delete tasks

View tasks

View workload layout

View tasks

Add, edit, and delete projects

Viewing projects where the user is a member, and viewing companies

Add, edit, and delete budgets

Viewing budgets where the user is a member, billable details, expenses, and the budget feed

Add, edit, and delete deals

Viewing deals, billable details, projects, expenses, and the deal feed

Add, edit, and delete draft invoices

Viewing invoices, expenses, time entries, billable details, and the invoice feed

Add, edit, and delete time entries for other people

Viewing and managing time entries

Add and manage employees and contractors

View employees and contractors

View agents

View AI Assistant

Why It Matters

Dependencies keep permission sets consistent. Someone can’t end up able to edit something they can’t see, or see something without the context it lives in.

👉 For every permission and its group, see Permission Groups and Permissions.

Did this answer your question?