Three administration scopes
| Scope | Primary responsibilities |
|---|---|
| Platform administrator | Onboard enterprises, manage platform-wide availability, operators, devices, add-ons, and bug reports |
| Enterprise administrator | Create and manage workspaces, manage users and enterprise settings, set the feature ceiling, read enterprise usage |
| Workspace administrator | Manage members, roles, setup, feature narrowing, and distribution inside one workspace |
The Admin Console
Administrators reach the console from the Admin Console chip at the top of MSOCK Studio. It opens its own shell, at the scope your role permits, and the brand mark in its corner is also the module switcher back to the rest of MSOCK.
| Scope | Sections you see |
|---|---|
| Platform | Enterprises · Provisioning · Audit log · Devices · Bug Reports · Add-Ons, and Configure: Operators · Features · Platform settings |
| Enterprise | Manage: Overview · Workspaces · Users · Features · Settings, and Reports: Usage Telemetry |
| Workspace | Workspace: Distribution, and Reports: Usage Telemetry |
The feature ceiling rule
A workspace can narrow what its enterprise permits, but it cannot widen it. If a workspace setting looks enabled while the capability remains unavailable, check the enterprise-level state, role requirements, and desktop-or-web availability.
Feature states and inheritance
Each product area has an availability status that decides the default when no explicit toggle exists. Generally available capabilities default on; limited-availability and coming-soon capabilities default off. An enterprise or workspace can then record an explicit override.
See product areas and access for the full feature list and current statuses.
Four role dimensions
A member holds one role from each of these, independently:
| Dimension | Values |
|---|---|
| Administration | Platform admin, enterprise admin, workspace admin, or none |
| Workspace persona | Engineer, Capability Lead, Guild, Product, QA, Security, Release Manager, Leader |
| SOCK role | SOCK Consumer (read-only), SOCK Creator, SOCK Knowledge Custodian |
| Platform operations | Platform Admin, Platform Operator, Platform Support |
A member can be, for example, an Engineer and a SOCK Creator and a workspace admin.
How membership becomes active
Adding a new person creates the account and grants workspace membership in one operation. There is no invite token and no acceptance link. The person appears as Invited immediately, and becomes Active the first time they sign in with the invited email address.
Workspace lifecycle
- 01
Create the workspace
An enterprise administrator creates it. At this point it is an administrative container with an immutable identifier.
- 02
Set up the workspace
A workspace administrator runs the one-time desktop setup, which publishes the organ pack and unlocks the modules for the team.
- 03
Bring in existing knowledge, if any
Optionally upload an existing SOCK documents folder for workspaces migrating from an earlier setup.
- 04
Add members
Add people, assign personas and SOCK roles, and grant workspace admin where needed.