Demo Accounts Permissions for Connections
Part of the MountDev Ops Demo Accounts documentation. Updated November 14, 2026
MountDev Ops Demo Accounts documentation | Updated November 14, 2026
These are the permissions a connection can hold in Demo Accounts. Each one is a single action. Pick only what the connection needs. A connection acts as the member who made it and never does more than that member could.
| Permission id | Level | What it does | Inputs |
|---|---|---|---|
demo.create | Write | Make a demo account with made-up data from an industry starting set | name (required), industry (required), apps, about, experience |
demo.experience_update | Write | Change what a demo account's people see at /account while it is being made | id (required), experience |
demo.list | Read | See your demo accounts, their state, and when each ends | before_id |
Make a Demo Account with Made-Up Data from an Industry Starting Set
Permission demo.create | Write | MCP tool demo_create (action demo.create)
POST /account/api/v1/actions/demo.create
{"name":"Example","industry":"landscaping"}Change What a Demo Account's People See at /account While It Is Being Made
Permission demo.experience_update | Write | MCP tool demo_experience_update (action demo.experience_update)
POST /account/api/v1/actions/demo.experience_update
{"id":1}See Your Demo Accounts, Their State, and When Each Ends
Permission demo.list | Read | MCP tool demo_list (action demo.list)
POST /account/api/v1/actions/demo.list
{}