Admin management

How a company gets a Dropstone organization: contact sales, describe what you want and why, and wait for a person to review the application. What to include, what you get once approved, and how long each step takes.

What each section of your organization dashboard holds, from members and teams to usage, billing, policies, the audit log, and the conversation archive. And who can see which part.

The six roles in a Dropstone organization, what each one may do, why reading member conversations is deliberately not an administrator power, how administrators are appointed, and what the gold verified mark means.

Active, on hold, suspended, cancelled, and terminated. What each state does, why only two of them can be reviewed, and what happens to your work in each.

How to ask for a review when an organization is on hold or suspended, what to include, how the review is tracked, and why cancelled and terminated accounts cannot be reviewed.

How an organization is billed: seats bought and managed in the dashboard and paid through a payment portal, or an Enterprise agreement invoiced by purchase order. Who can see it, and where invoices live.

Every administrative action in a Dropstone organization is recorded, with filters, ranges, and a CSV or JSON export. What is in it, who can read it, and why nobody can edit it.

The five controls on the organization's Security page: an identity provider, requiring single sign-on, provisioning on first sign-in, directory sync over SCIM, and emergency access.