Workspace & members
Flowtlas separates workspace membership and application permissions from the people and crews assigned to operational work.
The operational problem
A technician may appear in a crew while a dispatcher, planner or administrator needs a very different set of application permissions.
Workspace access management keeps membership, roles and permissions explicit so responsibilities can be reviewed without relying on one shared login.
Product capability
Manage which authenticated users belong to the workspace.
Assign responsibility-based access for viewing, editing and administration.
Review and update access when team responsibilities change.
Control authorized access to extension and workspace configuration where enabled.
Practical workflow
Describe what the member needs to view, change or administer.
Apply the role and any supported workspace-specific access.
Confirm that available screens and actions match the responsibility.
Update access when ownership, employment or duties change.
Operational benefits
In practice
A dispatcher reviews active work, a planner prepares and calculates routes, and a workspace owner manages members and configuration.
Each person receives the permissions needed for that responsibility. A crew assignment alone does not grant any of them application access.
Questions
No. Operational resource records and authenticated workspace membership are separate.
Yes. Available permissions distinguish supported read, manage and administrative responsibilities.
No. Workspace access and enabled functions must be confirmed for the deployment.
Work with operational context
