Guides › Start here
Team, Roles & Access Invite your team, give each person the right role, and scope agents to the leads they should work. Find it: Organization > Workspaces & Users. in the left sidebar of your workspace Before you start: An administrator role — only admins can invite people or change a role. The email address of each person you are inviting. A decision about who sees what: agents see leads for their assigned tags, procurement sees the whole pool with pricing.
Invite a teammate Press Invite team member Invite team member opens the form: enter the email and pick the role. The dropdown only offers roles you are allowed to grant. Send the invitation The person appears in the list with that role. Their access begins when they accept, not when you send.
The roles Role Sees and does Cannot Administrator Runs the workspace: people, tags, automations, schedules, billing. Sees every lead. Add another admin — the platform does that on request. Procurement The whole pool with pricing, and can purchase. Open settings or billing, or invite anyone. Agent Only leads carrying the tags you assign them. See pricing, or manage anyone. You can add and act on people below your own level — as an admin, Procurement and Agents. Procurement and Agent are peers; neither manages the other.
Practice: what each role reaches Click a role to see what it can open, then try the invite form.
Scoping an agent to the right leads The most consequential thing on this page, and the easiest to get wrong. Assign the tags Open the agent's row and pick from Scoped tags . Create tags first under Settings → Lead Tags . Set Match mode Any — lead has at least one of these tags is the usual choice and widens the view as you add tags. All — lead has every one of these tags narrows fast. The agent's Clearing Pool shows only matching leads, enforced on the server. An agent with no tags sees an empty pool No error message — just nothing. It is the most common “the product is broken” report from a newly invited agent; the fix is to assign a tag. The agent scope form, field by field
Change or remove someone's access Change a role or revoke access from their row You can act on anyone below your level. Update your own profile from the same panel Removing your own admin rights is not offered — the workspace would be left with nobody who can restore it. A role change ends that person's session everywhere, immediately — see Sessions . The In CRM column shows whether each agent and procurement member exists in your connected CRM — see Which of your people are in the CRM .
Sub-workspaces Give each team, office or partner its own people and leads, billed through you. Add a sub-workspace In Workspaces & Users : a name, and the email of the person who will be its admin. That admin is emailed an invite. They run their own team and leads without seeing anyone else's. Manage it from the parent when you need to Rename, suspend, reactivate or remove it, and manage its people yourself. There is no billing setup for them. Who Can You (parent admin) Create, rename, suspend, delete your sub-workspaces; invite and manage their users; see their leads. Sub-workspace admin Runs their own team and settings. No billing. Cannot create further sub-workspaces. Procurement / Agent Work leads within their workspace. They manage no one. Deleting a sub-workspace removes its users and leads Suspend it instead if you may want it back. Sub-workspaces are one level deep, and charges roll up to the parent: one consolidated invoice with a per-team breakdown, and sub-workspace admins never see billing — see Billing & Plans . How sub-workspaces are organized You'll know it worked: The person appears in the list with the role you chose, and an invitation reaches their inbox; access begins when they accept it. A sub-workspace appears nested under the parent with its own member list, and its charges appear on the parent's invoice rather than one of its own. A new agent sees nothing They have no scoped tags, or Match mode is All and few leads carry every tag. I cannot invite another admin Adding an Admin is done by the platform on request, so no single account can quietly hand out full control. I need someone out right now Change their role or suspend their account — both end their session immediately, everywhere. Who did what, and when? The security log — see Security . Why scope is enforced on the server An agent's view is built from the tags on their row, applied on the server on every read. It is not a saved filter they can clear or a URL they can edit, so it holds however they reach the data — including through connected applications. Every extra tag in All mode is another condition the same lead has to satisfy, and most leads carry only a handful, which is why Any is the usual choice. Authority flows down, never up: you can only assign or act on roles below your own, sub-workspaces cannot create their own, and adding an admin goes through the platform.