Overview
Use this checklist during the first week after creating a Scrambl workspace. It is designed for admins and implementation leads who need a practical launch path, not a perfect all-at-once configuration.
By the end of the week, your team should know where work lives, who can access it, how core records connect, and which settings still need deeper configuration.
Definition of ready: A workspace is ready for broader rollout when a new user can open a sample record, understand the workflow, complete a task, and find help without asking an admin for every next step.
Who can do this
- Owners and admins only: This is controlled by the workspace role (Owner or Admin), not by an access level, so it cannot be granted to other members.
- Personal accounts: Only the space owner and admins can do this.
Owners and admins review and change access levels in Settings → Administration → Members → Access levels.
First-week checklist by phase
| When | Owner | Checklist | Outcome |
|---|---|---|---|
| Day 1 | Workspace admin | Confirm organization settings, timezone, regional preferences, and terminology in Settings. | Records and dates use the right defaults. |
| Day 1 | Workspace admin | Create one sample client or internal account, one sample project, and several sample tasks. | The team has a concrete workflow to test. |
| Day 2 | Admin and team leads | Invite the core team from Settings → Administration → Members and review each person's role and access level. | People can sign in with appropriate access. |
| Day 2-3 | Operations lead | Configure task statuses and project workflow conventions in Project Settings. | Task movement reflects the way the team actually works. |
| Day 3-4 | Workflow owners | Confirm time, billing, approvals, and invoice settings if those workflows are used. | Sensitive operational and finance flows are tested before launch. |
| Day 4-5 | Admin | Connect priority integrations in Settings → Administration → Integrations. | External tools are connected only after workspace structure is stable. |
| Day 5 | Admin and pilot users | Search help, ask Benny where available, and confirm users can find guidance. | Support habits are established before the team scales. |
Detailed checklist
Workspace settings
- Confirm the organization profile and workspace name.
- Confirm timezone and regional preferences.
- Review terminology so labels match how your team speaks.
- Check whether any modules should be hidden through permissions before launch.
People and access
- Invite owners, admins, team leads, and a small pilot group first.
- Assign roles and access levels based on current responsibilities.
- Review sensitive access for finance, billing, integrations, permissions, and subscription settings.
- Confirm pending invites have been accepted before training sessions begin.
Sample records
- Create one sample client or internal account.
- Create one sample project that represents a real type of work.
- Add sample tasks for common states such as not started, in progress, blocked, review, and done.
- Assign tasks to pilot users and ask them to update status, comment, and complete one task.
Workflow settings
- Review project and task statuses in Project Settings.
- Confirm whether projects need phases, task groups, or standard naming rules.
- Check time and billing settings before asking users to enter real time.
- Connect integrations only after the team agrees the sample workflow is stable.
Readiness review
| Question | Ready when |
|---|---|
| Can a new user find their assigned work? | They can open Today, Tasks, or a project and identify what to do next. |
| Do permissions feel correct? | Users can access what they need and cannot access sensitive areas they do not manage. |
| Are workflow terms clear? | Statuses, project names, task groups, and module labels match team expectations. |
| Are support paths obvious? | Users know where to find Help, search workspace records, and ask for guidance. |
Common issues
- Too much setup at once: Pause nonessential configuration until the core workflow is proven.
- Missing owners: Assign an owner to every launch task so setup work does not drift.
- Unclear sample data: Use realistic names and mark test records clearly so users can learn without confusing sample work for production work.
Next steps
After the checklist is complete, replace or archive sample data, invite the broader team, and schedule a permissions review after the first real week of work.