Scoping members to projects and capping spend

Project scope

By default, a new member can open every project in your organisation. That is often more than you want, especially for a contractor or a client-side reviewer. You narrow it per person on the Team tab, and each member's project scope can be set to one of three things:

• Org-wide: every project, including ones created after they join.
• A specific list: only the projects you pick, nothing else.
• No project access: they stay in the organisation but cannot open any project at all.

Scope is your tool for limiting reach. It is the difference between a building pass that opens every door and one that opens a single floor, which is exactly what you want when you keep a freelancer on one client's project and out of everything else.

Monthly credit cap

Credits are a shared pool, which means that, left unchecked, one member could burn through the whole balance in an afternoon. To stop that, set a per-member monthly credit cap. From then on that person can spend up to that many credits each month and no more, no matter how much the organisation has sitting in the pool.

Requesting access

A member scoped out of a project they genuinely need is not stuck. They can request access to it, and an owner or admin approves or declines the request. The project access requests help walks through that flow from both sides, the person asking and the admin deciding.