In short
Start with one real activity, enable only the modules it needs, then choose either direct project access or a Team. Assign roles before adding operational data.
On this page
Before you create anything
Decide what the project should accomplish and who is responsible for it. A project works best when it represents a concrete programme, camp, unit, equipment store, or season.
- Use a name people will recognise in the workspace.
- Identify the Owner who will control access and deletion.
- List the smallest set of modules needed on day one.
Create your first project
From the workspace, choose New project, enter its name, select modules, and accept the data-processing agreement if you are authorised to do so.
Step by step
- 1Open your workspace and choose New project.
- 2Name the project after its real purpose.
- 3Select Attendees, Attendance, Inventory, or a valid combination.
- 4Review the data-processing agreement and create the project.
- 5Open Project settings and confirm the module list.
Choose an access model
A project uses one membership model at a time. Direct access suits a unique roster. A Team suits people who repeatedly work across several projects.
- Direct: invite users in Project settings and assign access one person at a time.
- Team: maintain one Team roster and assign project roles and modules centrally.
- Do not duplicate the same people through both models; Scoutzy intentionally prevents that ambiguity.
A reliable launch sequence
Configure governance before entering sensitive or operational data. This prevents accidental overexposure and makes ownership clear.
Step by step
- 1Assign Admin, Editor, and Viewer roles.
- 2Restrict Editors and Viewers to the modules they actually use.
- 3Create event types before building an attendance calendar.
- 4Add attendees or inventory items.
- 5Run one test workflow and review the result together.
Put this into practice
Use this browser-only checklist during your next review.
0/5Common questions
Can I change the setup later?
Yes. Names, modules, roles, and module scopes can change. Moving a direct project to a Team requires removing non-owner direct members and pending invitations first.
Do attendees need Scoutzy accounts?
No. Attendees are operational records. Project members are authenticated users who manage the project.