Platform owner
Prepare the environment
Manage hosting, the database and platform connections. Keep test data and credentials separate from production. Access to a hosting provider is separate from an app role.
From setup to connected work
Know who sets it up.
Know what it can do.
A useful workflow starts with clear responsibilities. Give project creators a practical starting point, keep administration with the right people, and verify integrations before they touch real work.
01 / Your responsibility
Start with your role
Project ownership, membership, explicit permissions and plan limits work together. Creating a project does not make someone the platform owner.
Organization admin
Prepare the team
Manage your organization’s members, plan and supported connections. Decide who needs project access. Organization administration does not grant platform-wide control.
Project creator
Prepare the workflow
Choose a template, check plan capacity and verify the created project. Review example data and automations before connecting real systems. Creation requires the appropriate permission.
Member or viewer
Work within your access
Use the projects and actions your account permits. Shared showcases are for exploration; a personal sandbox or explicit project membership can have different permissions.
A repeatable setup, in four steps
- 1
Choose a workspace
Start with a template that matches the work. Check the project’s queues, dashboards and examples after creation.
- 2
Assign responsibility
Separate project work from organization administration, provider credentials and local machine installation.
- 3
Test with separate data
For integration work, use a verified test environment and synthetic records. Start with one read and one controlled update.
- 4
Verify and clean up
Reload the result, check the connected system when applicable, and remove only the test records you created.
02 / Connect with context
Use today’s API. Understand what’s next.
Authenticated project and item operations
The application uses authenticated API calls to manage projects and items. Those calls remain subject to account permissions and resource access. Browser mutations also require session and request-forgery protection.
Legacy API keys are managed by the platform owner and work with selected endpoints. They are not general project-scoped CRUD credentials. A paid plan’s key allowance does not change that boundary.
Review integrationsScoped access for clients and workflows
The proposed direction is credentials limited to an organization, selected projects and allowed actions, with expiry, revocation and an audit trail.
Automations, playbooks and sync would use the same permission policy through an explicit execution identity. This design is not an enabled feature or an entitlement included in a plan today.
Tell us about your integrationAlready use a password manager such as Bitwarden? Keep dedicated test credentials there and supply only the credential a supported client needs. Automatic vault access or a built-in Bitwarden integration is not included.
For Creator and Extend workspaces
Use Extend Platform to organize machines, tool inventory, health checks and content work. Installing tools still belongs to the machine operator. Example health values and command queues do not prove a desktop bridge is connected or executing actions.
See what the Extend template coversStart with a project you can verify
Explore the current app, choose a template, and bring us the workflow you want to connect.