What this document covers
When someone uses our product for the first time, certain things need to be in place before they can work productively. Provisioning is the name we give to that automatic, behind-the-scenes setup that runs when a person is ready to use the system. It is separate from any optional guided tour or checklist we may show in the product to help new users learn the ropes.
This note explains what provisioning means for you and your people—without implementation detail.
What happens at first use
Goal: The person can sign in once and already have a place to work—nothing manual required from your administrators for the basics.
In practice, provisioning typically ensures that:
- The person is recognized as a user of your environment.
- They receive a default workspace (we use a clear label such as My workspace) so they are never stuck without a context to work in.
- They are connected to that workspace in the right role from day one, so they can act as an owner of their own area unless your organization’s rules say otherwise.
- A simple organizational home exists for that workspace, so the product can grow with you as you add structure later.
All of this is automatic the first time the user is in a state where the product can complete setup. There is no separate “create my workspace” form required for the basics.
Provisioning vs. the guided "getting started" experience
| Topic | Provisioning (automatic setup) | Optional product tour / checklist |
|---|---|---|
| Purpose | Make the user ready to work in a valid workspace. | Help the user learn features and complete recommended steps. |
| When | Runs in the background when appropriate at first use. | When the person opens the guided experience, or when follow-up activities occur in the product. |
| What you see | You land in a working workspace; you can start. | You may see steps, progress, or prompts to finish “getting started.” |
| Required? | Yes—so every user has a place to work. | No—your work is not blocked if you skip it. |
Summary: Provisioning answers “Do I have a place to do my work?” The optional guided flow answers “Would you like help learning what to do next?”
What this means for your organization
- Faster time-to-value: New users are not waiting on a manual provisioning ticket before they can open the product meaningfully.
- Consistent experience: Everyone starts with a clear default that your admins can build on (additional workspaces, policy, and structure as you define them).
- Clear split of concerns: Infrastructure readiness (provisioning) is not mixed with product education (the optional checklist), so reports and expectations stay easy to explain.
Security and data boundaries (plain language)
- Each user’s default workspace is their working area; work you do there is scoped to the right team and organization in the product so that visibility follows your rules.
- Provisioning only prepares what is needed to operate; it does not replace your organization’s own policies for access, offboarding, or who may join which workspace.
For contract-specific data residency, sub-processors, and certifications, please refer to your agreement and our security documentation.
Questions we often hear
Do we have to “turn on” provisioning?
For standard use, it is part of how the product welcomes new users. If you have special requirements, your account team can walk through options.
Does provisioning replace our identity system?
No. Your sign-in and identity process stays in charge of who the person is. Provisioning is what the product does after that to give them a workspace to work in.
Can we add more structure later?
Yes. The default setup is a starting point. Many customers add named workspaces, more teams, and governance as they grow.
If you need a version of this content tailored to an RFP, security questionnaire, or executive one-pager, we can provide a fit-for-purpose variant.