Confirm who approves access, which workspace mode you are in, and which setup steps belong to your administrator versus Bundata.
Before you start
Use this checklist before anyone uploads a file or connects a source. It separates what your organization must decide from what Bundata operates. It does not mean every person needs a personal provider key, and it does not offer a self-service paid upgrade.
Checklist
| Check | What to confirm | Owner |
|---|---|---|
| Client administrator | A named owner or admin who can invite people and change organization settings | Client |
| Approved access | The person can sign in to the workspace they were granted. Public signup may be closed | Client administrator, with Bundata when enrollment is closed |
| Workspace mode | Stored, or a dedicated non-retaining workspace. These paths do not mix | Client administrator |
| Access level | Owner, admin, editor, or viewer. Extraction and upload need more than viewer | Client administrator |
| Allowed data | Fictional sample pack, or files your organization has authorized | Client |
| Generation credential | Organization OpenAI or Anthropic key, only if a feature on this workspace calls a generation model | Client administrator |
| Embedding profile | Which of the three exposed profiles the workspace uses, and who supplies its prerequisite | Client administrator or Bundata operator, depending on the profile |
| Storage, index, and workers | Object storage and the processing queue are available for stored uploads | Bundata operator, unless your deployment agreement says otherwise |
| Provider cost | The organization that owns the provider account pays that provider | Client, for organization-owned keys |
| First result | You know whether you are following the stored journey or the non-retaining journey | Client |
What this checklist does not assume
- A viewer does not create provider keys.
- Selecting an embedding model does not provision that model or migrate collections that already have a profile.
- A connector listed in a picker is not proof that ingest or destination writes are enabled.
- Documentation is not approval to process customer content in a live environment. If a provider or runtime is blocked, stop and escalate with the workspace id and the error code. Do not paste keys or document text into a ticket.
Next step
Sign in and confirm the workspace in Access and roles. Then choose Quickstart for a stored workspace or Non-retaining path for the limited file path.