Overview
Workspace setup is the first admin pass that turns a new Scrambl organization into a place where real work can happen. Use this article when you are launching a workspace, resetting a pilot environment, or preparing a small team before a broader rollout.
The goal is not to configure every possible module on day one. The goal is to confirm the organization basics, create a realistic sample workflow, invite the right people, and connect only the integrations that are needed for the first week.
Best practice: Complete setup with one sample client, one sample project, and a few sample tasks before importing production data. A small test workflow exposes permission, terminology, and status issues early.
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.
Before you start
- You should have admin access to the workspace.
- You should know the workspace timezone, regional defaults, and preferred team terminology.
- You should know which modules the team will use first, such as Clients, Projects, Tasks, Time, Contracts, Invoices, or Inventory.
- If you plan to invite teammates during setup, collect their email addresses and decide which roles and access levels they need.
Launch sequence
| Phase | Where to go | What to confirm |
|---|---|---|
| Organization basics | Settings | Profile, timezone, regional preferences, terminology, and workspace defaults. |
| Starter workflow | Projects and Tasks | One sample client or internal account, one project, task owners, statuses, and due dates. |
| Team rollout | Settings → Administration → Members | Core team invites, role assignments, access levels, and sensitive access. |
| Integrations | Settings → Administration → Integrations | Only the tools needed for launch, such as Slack, email, calendar, or accounting connections. |
Step 1: Confirm organization settings
- Open Settings.
- Review the organization name, profile details, timezone, regional preferences, and date or currency-related defaults.
- Confirm any terminology your team expects to see. For example, decide whether teams say clients, accounts, projects, jobs, or another term in daily work.
- Save changes before creating sample records so new records inherit the correct defaults.
Step 2: Choose the first modules
Start with the smallest set of modules required for the first real workflow. A professional services team might begin with Clients, Projects, Tasks, Time, and Invoices. An operations team might begin with Projects, Tasks, Calendar, Documents, and Inventory.
- Use now: Modules the team must touch during the first week.
- Configure later: Modules that need policy decisions, such as advanced billing, forecasting, or external collaboration.
- Hide through permissions: Modules that should not appear for every teammate.
Step 3: Create a sample workflow
Create one realistic record chain so admins can test how Scrambl connects work across modules.
- Create one sample client or internal account.
- Create one sample project connected to that client or account.
- Add three to five tasks with clear owners, statuses, and due dates.
- If your team tracks time, add one test time entry against the sample task.
- If your team bills through Scrambl, create a draft invoice or billing example and confirm it remains a test record.
Example: Create a client named Acme Pilot, a project named Website Launch Pilot, and tasks named Confirm kickoff agenda, Draft project timeline, and Review launch checklist. This gives new users a concrete path to follow.
Step 4: Invite the core team
After the sample workflow is ready, invite the people who will validate it. Start with owners, admins, operations leads, finance leads, and one or two daily users. Use Settings → Administration → Members to send invites and review access.
- Give each person the smallest role and access level that lets them complete setup tasks.
- Hold finance, billing, integration, and permission management access for trusted admins.
- Ask invited users to open the sample project and confirm they can see the right modules, tabs, and actions.
Step 5: Add integrations when the workflow is stable
Connect integrations after the team agrees the basic records, permissions, and statuses make sense. This prevents external tools from syncing test data or notifying people before setup is ready.
| Integration type | Connect when | Check before rollout |
|---|---|---|
| Slack or chat | The team is ready for workspace alerts. | Notification channels and mention behavior. |
| Email or calendar | Users need scheduling or message context. | Connected account ownership and privacy expectations. |
| Accounting | Billing settings are approved. | Currency, tax, invoice, and customer mapping rules. |
Troubleshooting
| Issue | What to check |
|---|---|
| A teammate cannot see a module. | Review their role and access level in Settings → Administration → Members. |
| Dates or times look wrong. | Confirm workspace timezone and the user's local preferences. |
| People are unsure where to start. | Send them to the sample project and the Help Center getting-started articles. |
| Test data is mixing with real work. | Rename test records clearly, archive them, or delete them before importing production data. |
Next steps
- Invite the rest of the team after the core workflow is approved.
- Use the first-week checklist to track launch readiness.
- Review permissions again after real projects, clients, and billing workflows are added.