Every company in BlossomERP has a company administrator: the person (or people) holding the company-admin role for that company. Inside the company, that authority is complete — users, roles, setup, switches, imports: this chapter's whole territory. Two boundaries define the role honestly:
- The ceiling is the company. Platform powers — the plans themselves, the platform's payment gateways, signing in as another company's user — belong to the platform's super-administrator, and cannot be granted from inside a company, by anyone, to anyone. (The rule at 16.2 is the mechanism.) If a task needs the platform team, that is not a failure of your admin rights; it is a different desk.
- Deleting is reserved. Across the whole application, deletion belongs to the platform's highest role alone (1.12) — administrators keep things tidy by deactivating instead: users, accounts, banks and categories all carry an Active switch, and deactivated history stays readable.
- The Model company is read-only. One company on the platform is flagged as the Model — the template whose chart, units, categories and settings every new company starts from. It is labelled MODEL wherever companies are listed or picked, and a banner says so while you are in it. If your work ever takes you into the Model, you can look everything up, but you cannot change anything there: the create, edit and delete actions are simply not offered, and only the platform's super-administrator can update the Model — because every change to it becomes the defaults the next new company inherits.
Your work splits between Chapter 0 (setting a company up, and reconfiguring it later) and this chapter (the daily care of a running company): who can do what, the setup screens as a tour, bringing data in, and the trail that answers for all of it.