Best practices for workspace setup
Last updated: 7 May 2026
What this does
Use this guide to set up an IMPACT workspace so teams, projects, permissions, and entitlements are easy to manage before daily work begins.
Current access and functionality
- Verified against the current
impact-web,impact-client, andimpact-marketplacecode on 2026-05-07. - Workspace setup is primarily done in
impact-webby owners and admins. impact-clientreflects the workspace setup for staff day-to-day work, including workspace selection, projects, tasks, checklists, surveys, notifications, and marketplace usage.- Module visibility depends on role, permission, feature flags, subscription entitlement, workspace assignment, and member assignment.
Recommended setup order
- Confirm company profile, workspace name, and basic settings.
- Review subscription and entitlements before promising module access to users.
- Invite admins and team leads first.
- Create teams that match how work is actually managed.
- Add staff to the correct workspace, team, and project context.
- Create the first projects or import approved templates.
- Set checklist templates for repeated work.
- Confirm staff can sign in from
impact-clientand see the expected work.
Naming conventions
- Use short workspace names that staff can distinguish on mobile.
- Name teams by operating responsibility, not only department labels.
- Keep project names specific enough to search and identify.
- Use template names that explain when to use the template.
Access rules
- Give admin access only to users who manage setup, billing, permissions, or templates.
- Use team lead or project manager access for operational control without making everyone a workspace admin.
- Review entitlement limits before adding members, AI Employees, or advanced modules.
- Check both workspace membership and project/team assignment when a user cannot see work.
Common issues
- Issue: A staff user sees an empty mobile app. Fix: Check workspace selection, membership, team/project assignment, and task assignment.
- Issue: An admin cannot see a module. Fix: Check subscription entitlement and feature flags, not only role.
- Issue: Users are confused by similar workspace names. Fix: Rename workspaces with clear company, branch, or environment identifiers.