Dropstone for teams and organizations
An 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.
An organization is how a company uses Dropstone together. It puts every member under one structure with one bill, lets you group people into teams, and unlocks the things that only make sense with more than one person: shared memory, single sign-on, and provisioning.
What an organization gives you
One bill. Members are covered by the organization's plan. Nobody expenses a personal subscription.
Members and teams. Add people to the organization, then group them into named teams: Platform, Growth, Data, whatever matches how you work. Teams matter for shared memory.
Shared memory. What one engineer teaches Dropstone can be shared with their team or the whole organization, so the assistant knows your conventions, your deploy process, and your decisions without each person teaching it. See Shared memory across a team.
Enterprise sign-in. Single sign-on through your identity provider, and SCIM provisioning so joiners and leavers are handled automatically.
Isolation. An organization's memory, conversations, and files are never visible to any other organization or to personal accounts outside it.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including billing, deleting the organization, and transferring ownership |
| Admin | Manage members, teams, SSO, SCIM, and shared memory |
| Member | Use Dropstone; share their own memories to their team or organization |
An organization has at least one owner. Owners and admins manage the organization from the dashboard.
Setting up
Organizations are on the Enterprise plan and are set up with us directly. Start from the contact page or How to get support. The application is described in Get an organization for your company. Once the organization exists, its owner adds members and creates teams from the dashboard, or connects SSO and SCIM so membership follows your identity provider.
Members keep their own memory
Joining an organization does not hand over a member's private memory. Every memory starts private, and only becomes shared when its author shares it. A member's conversations and projects stay theirs. See Memory in teams and organizations.
When someone leaves the organization, their private memory leaves with them. An admin can remove any memory that had been shared to a team or the organization at any time, and organizations can set a retention window after which shared memory is retired automatically. See Shared memory across a team.
Data handling for organizations
Organization data is subject to the same handling as everything else, with the isolation guarantees above. Enterprise customers can request a data processing agreement; see How Dropstone handles your data.