Organizations
Organizations in Blueputto separate workspaces, members, roles, folders, collections, and billing, with easy switching, setup, and management tools.
Grzegorz
Organizations are the top-level workspace boundary in Blueputto. Each organization carries its own members, teams, roles, folders, collections, documents, items, and billing state, which makes it the cleanest way to separate museums, departments, clients, or internal programs inside one account.
That separation matters because Blueputto is not a single shared database with a cosmetic switcher on top. The active organization changes what the rest of the application shows and what limits or permissions apply.
The active organization changes the rest of the app
Blueputto exposes organization switching in two places: the account-level Organizations page and the main app sidebar. From the sidebar dropdown, users can see the current workspace, switch to another one, and immediately continue in that new context.
That switch is operational, not decorative. Home, Documents, Items, Members, plan usage, and settings all resolve against the active organization. Changing organizations means changing the collections, documents, teammates, and rules that the rest of the UI works with.
Create, join, leave, or delete from one account area
The Organizations settings page gives each account a table of available workspaces, with the organization name, current plan badge, created date, and a row action menu.
From there, users can:
create a new organization by entering a name,
switch into another organization,
leave an organization they do not own,
and delete the currently active organization when they are allowed to remove it.
Joining happens from the invitation side of the product. When someone accepts an organization invitation from email, that workspace becomes part of their account and appears in the same switchers and organization list.
Deletion is intentionally stricter than leaving. In the current implementation, owners cannot delete an organization with an active paid subscription, and they also cannot delete their last remaining owned organization. That keeps workspace cleanup from turning into accidental lockout.
New organizations start with real structure
A new organization does not start blank. In the current implementation, creation immediately places the workspace on a 14-day Scale trial and seeds a practical museum-oriented starting structure.
That seeded setup includes:
default labels such as
Acquisition,Conservation, andResearch,starter folders such as
Collection ManagementandLoans & Deposits,starter collections such as
Paintings,Sculptures, andArchaeology,starter categories and status groups,
and default document templates.
Those defaults are also language-aware, which makes the first-run workspace more useful before the team has customized Folders, Collections, Statuses, or Plan and Billing.
