Data & Security

Roles Your Team Recognizes.. Access the Work Defines

Built-in roles do not always match how your team works. Create a role in your team's language, scope exactly what it can see and do, then assign it wherever it is needed.

Your accountant needs reports but should never touch tasks.. an external collaborator works on one project only.. an operations assistant tracks progress without editing it.

Built-in roles rarely describe all of them. So you make a bad trade-off: give someone too little access and they stop to ask at every step, or give them too much and expose work they should never see or change.

Custom Roles in Fareeqy end that trade-off. The company owner creates a role in Company Settings, names it the way the team actually speaks, such as “Accountant”, “Content Reviewer”, or “External Collaborator”, then defines exactly what it can see, create, edit, and never touch.

What you build once keeps paying off. When someone joins in the same capacity, assign the ready role instead of setting permissions line by line. When policy changes, edit the role once and the update applies to everyone who holds it.

Because permissions are a matter of trust, creating and editing roles belongs to the company owner and to anyone the owner explicitly grants the “Manage roles and permissions” permission. Everyone else cannot widen their own access. Roles also work alongside project membership, so an external collaborator sees only the private projects they were added to. It is how law firms organize their work: a private project for every matter, and a role for every position in the firm.

The result? Every member can work freely inside the exact scope their job requires. No excess access waiting for an accident, no repeated approval requests, and no manual permission review whenever someone joins.

Custom roles and permissions are available on the Advanced, Productive, and Enterprise plans.

How Custom Roles Work

Roles Your Team Recognizes

Use names such as “Accountant”, “Content Reviewer”, or “External Collaborator”. Your roles match the way your team actually works.

Precisely Scoped Permissions

Define what each role can see, create, edit, and never touch. No fixed permission bundle to accept as-is.

No Excess Access

Each member gets only what their work requires. Sensitive projects and destructive actions stay out of reach.

Faster Member Setup

Someone joining in the same capacity gets the ready role instead of permissions configured line by line.

One Edit Updates Everyone

Change a role once and the new permissions apply to every member who holds it.

Owner Controlled

Roles are created and edited by the company owner, or by someone the owner grants “Manage roles and permissions”. Nobody else can widen their own access.

Key Benefits

A role shaped around each job instead of a fixed title that does not fit
No broader access than a member needs
External collaborators see only the private projects they join
New members receive a ready role instead of line-by-line setup
One role edit updates everyone who holds it
Only the owner, and whoever the owner trusts with it, can create or change roles

Frequently Asked Questions

Who can create a custom role?
The company owner, and anyone the owner grants the “Manage roles and permissions” permission. That is a permission of trust, because its holder can grant any permission short of the owner role, so give it only to people you trust. Every other member cannot widen their own access or grant new access to someone else.
Which plans include custom roles?
Custom roles are available on the Advanced, Productive, and Enterprise plans. The Free and Pro plans run on the built-in roles. See pricing details.
What happens to custom roles if I downgrade?
No member is left holding permissions your plan can no longer manage. Before moving to a plan without custom roles, Fareeqy asks you to delete them first, choosing for each one the built-in role its members move to. Then the downgrade goes through.
Can a role restrict access to a specific project?
Yes. A role defines what a member can do, while project membership defines which projects they can reach. An external collaborator therefore sees the project they were added to, while every other private project stays out of reach. A public project is visible to everyone in the company.

Build Your Team's First Custom Role

Define exactly what each member can do, and nothing beyond it

Try It Free Now

Find it in: Company Settings → Roles & Permissions

✓ Free Forever • ✓ No Credit Card Required