Inviting your own people
Users and licenses, under Administration, is the master list: everyone in the organization, every invitation still in flight, what each person can open, and what each one costs. Invite someone there sends the invitation — you choose what they will be, and optionally which projects they join on day one.
A project's Team tab does the same thing for one deal, and is the right place when you are staffing that deal rather than hiring into the firm.
Each person gets a class, and the class decides what they can do: administer the workspace, run and approve analysis, author reports, or read.
Seats, and what an invitation costs
Classes that create deals, author or approve findings, or administer the workspace use a licensed seat. Contributors, reviewers and report readers never do. An invitation holds a seat open from the moment you send it — so the count you see already includes people who have not accepted yet, and withdrawing an invitation releases it again.
When there is no seat left, the product says so before you type rather than after you submit, and points at Users and licenses. If you are not the person who administers the plan, it names who is.
Roles are about authorship, not visibility alone
The distinction that matters for a diligence record is who can make a finding Reviewed. That action is a sign-off. Restrict it to the people whose judgment your firm is willing to stand behind, and the review trail becomes meaningful.
External participants
Three kinds of people who are not your colleagues may touch a project:
| Who | What they get |
|---|---|
| Target contributors | Add material against request items. They do not see findings, ratings or the report. |
| Report readers | A share link to an issued report, under whatever agreement you attached. |
| Reviewers | A share with markup rights: they can raise threads against the report, and you reply. |
None of them are billed as users, and none of them can see your analyst files or your drafts.
What an external reader can reach
A share is scoped to what you shared. It is not a way into the workspace: a reader with a report link cannot browse your other projects, your team, or your settings.
Removing access
Removing a team member ends their access immediately and leaves their review history intact — a sign-off stays attributed to the person who made it. Revoking a share link kills that link; anything already downloaded is, as always, out of reach of any system.
Availability
Team members are part of the plans that include collaboration. A single-user plan can still share reports externally.