Your organization dashboard
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.
Your organization lives at dropstone.io/org/<your-company>. It is where the organization is administered, and what each person sees there depends on their role, not on what they ask for.
What is in it
| Section | What it holds |
|---|---|
| Overview | Seats, credit pool, monthly spend, who has been active recently |
| Members | The roster, roles, and seats |
| Teams | Teams and who is in them |
| Memory | What the organization has taught Dropstone and chosen to share |
| Usage | Requests, cost, tokens, and cache savings, by member, model, and surface |
| Billing | Invoices, seats, and the subscription |
| Policies | Models, connectors, surfaces, tools, and network rules |
| Security | Single sign-on, provisioning, and emergency access |
| Audit | Every administrative action, with filters and an export |
| Conversations | The conversation archive, when content logging is on |
| Data | Content logging, retention, telemetry, and branding |
The three sections people ask about most
Usage shows counts and cost, never the contents of anyone's work, whatever the logging setting is. See What is recorded about every request.
Conversations is the archive, and it is empty unless the owner turns content logging on. Who can read it is deliberately narrow. See Read and export the conversation archive.
Data is where the three settings that decide what is kept live, and every change to them is written to the audit log. See How an organization manages its data.
Branding
Data holds a Branding section where the owner uploads the organization's marks: a square mark for the boxed places (the sidebar, an avatar) and a horizontal wordmark for the line-shaped ones (headers, email banners). Your logo replaces the Dropstone mark throughout the console, and appears on invitation emails and your sign-in page.
Where they land: the square mark is what a member sees beside their own name in the sidebars and in Settings, and the wordmark stands in for the organization's name at the top of the console.
Each slot accepts only the shape it can use, so it is two pictures rather than one picture at two sizes. Until a mark is uploaded, the organization's name stands on its own.
What is not in it
Your own conversations, your files, and your private memory. Those belong to the person who made them, and the dashboard does not expose them. The one exception is the archive, which records member conversations when the organization has asked for that, and which only the owner, the security role, and auditors can read.
Related articles
- Roles and permissionsThe 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.
- Billing for your organizationHow 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.
- The organization audit logEvery 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.
- How an organization manages its dataThe three settings an owner controls for an organization, what each one stores, who can read it, and the limits of the strongest setting. Content logging, product telemetry, and retention, in one place.
- Read and export the conversation archiveWho can read an organization's recorded conversations, how to search and filter them, what the archive never holds, and how to export it as JSONL.
- Dropstone for teams and organizationsAn organization gives a company one Dropstone account structure, centralized billing, members and teams, shared memory, and enterprise sign-in. What an organization is, roles, and how to set one up.