Skip to main content
Parlé uses role-based access at two distinct levels: the organization level and the project level. Org-level roles control who can manage firm-wide settings like SSO, billing, storage, and member rosters. Project-level roles control who can do what inside a specific project. A person can be a Member at the org level but a Project Admin on a particular client engagement — the two levels are independent. This two-tier model lets you give senior staff or engagement leads control over their own projects without granting them access to firm-wide configuration.

​
Role Overview

On the Business plan and above, a project can be Restricted (private): it is hidden from the project list for everyone who is not one of its members. Only its members — and Org Admins, who see every project — can see that it exists. This is designed for sensitive matters — restructuring work, partner-level engagements, or any matter where even the existence of the project is confidential.

​
Assigning Roles

1

Assign or change an org-level role

Go to Members in the sidebar. Find the member in the list and click their name or the role badge next to it. Select the new role from the dropdown. Changes take effect immediately.
2

Assign or change a project-level role

Open the project and go to the Members tab. Find the member and click the role badge next to their name. Select Project Admin or Member from the dropdown. Only Org Admins and that project’s Project Admins can change project roles.
3

Add a new member to a project

From the project’s Members tab, click Add Member, search for the person by name or email, select their project role, and confirm. They immediately gain access to the project’s conversations and files.
4

Remove a member from a project

From the project’s Members tab, click the menu next to the member’s name and select Remove from Project. They lose access to the project immediately. Their past contributions (messages, uploaded files) remain in the project record.

​
Project Visibility

Project visibility is strictly enforced on the server — it is not just a UI preference. Every project is either Public or Restricted:
  • A Public project can be opened by anyone in your organization.
  • A Restricted (private) project can be seen and opened only by the people who have been added to it as members. For everyone else it does not appear in the project list, and a direct link to it behaves as though the project does not exist. Restricted projects are available on the Business plan and above.
Org Admins are the exception. An Org Admin sees every project in the organization in the project list and can open any of them, Restricted ones included, so that they can manage its members, budget and settings. If a matter must be kept from a particular person, that person should not hold the Org Admin role.

​
Budget Increase Requests

Only Org Admins set a project’s spending caps — a monthly cap, a lifetime cap, or both, in the project’s own budget currency. A spend ceiling the spender can raise is not a cost control, so Project Admins and members see the caps read-only. See Budgets. When a send is blocked because the project has reached a cap, anyone on the project — a Member or a Project Admin — can select Request a higher limit directly from the conversation, or from the project’s Budget tab. An Org Admin answers the request from Requests in the sidebar: they choose which cap to raise, enter the new limit in the project’s budget currency, and approve it — or reject it with a reason. Requests and their outcomes are recorded in the audit log. Once approved, the new limit takes effect immediately and the member can continue their work.
Use project codes alongside budget caps to tie AI spend directly to client matter numbers in your billing system. Set the Project code on the project’s Project Details tab and it will appear in usage exports for easy reconciliation. See Expense Codes.