Skip to content
Console
Try one

    Team Workspace

    Prepare a shared workspace with plan rules, help ownership, and a clear first setup.

    Team workspace setup is for groups that need a shared path before creating many items.

    For a first setup, start with First Setup. For naming and access-rule examples, use the Scenario Playbook.

    The point is agreement before scale. A team that settles naming, access review, runtime changes, and who answers help questions before it has many hubs and connections doesn’t have to untangle them later.

    Four decisions cover most of it. One person creates the first hub, and creates it only after the plan limits and hub addresses are understood. One person, or one process, reviews any access rule wider than a single purpose. The first healthy loop of hub, connection, and access rules becomes the pattern everyone repeats. And runtime config changes only when a hub’s purpose genuinely needs different defaults, never as a first response to a problem.

    1. Review the workspace plan. Confirm hub limits, runtime slots, connection limits, policy limits, addresses, skill access, and help options in Billing.
    2. Confirm review and help options. Decide who handles account questions, plan questions, and hub or client questions.
    3. Prepare the first hub. Create the first hub only after the plan and help options are clear.
    4. Agree on runtime changes. Decide when to use workspace default skills and when a separate skill set should have its own runtime config.
    5. Create connections and access rules together. A client without access rules is harder to understand later.
    6. Use Dashboard and Topology. Make health and connections visible as soon as clients begin connecting.

    Use names that explain purpose, not just ownership:

    • support-frontdesk is clearer than client-1;
    • demo-public-general is clearer than test-hub;
    • frontdesk-questions-only is clearer than default-permissions.

    Good names make search, filters, Topology, and reviews easier to scan.

    Before the team creates many items, create one complete loop:

    1. One hub with a clear purpose.
    2. One skill set choice with runtime defaults left simple unless there is a clear reason to change them.
    3. One connection with a clear purpose.
    4. One access-rule set with narrow allowed actions and clear safety rules.
    5. One Dashboard review.
    6. One Topology review after the client is live.

    That loop becomes the template for future hubs, connections, and access rules.

    You’ll know the setup is ready to copy when a new teammate can explain the first hub, its connection, and its access rules without help. Everyone knows who reviews wider access. A runtime change has an obvious review path. Dashboard and Topology are part of the routine check, not the place people go after something breaks. Names that follow the same purpose-based pattern are the sign it has stuck.