Templates
A template is a reusable setup you can browse and apply instead of configuring everything from scratch. Where applets, widgets, and workflows are the building blocks, a template is a pre-assembled arrangement of them — a starting point you apply and then make your own.
Templates matter because a blank workspace is a cost. The extensibility model gives you plenty to configure, but most people don't want to design a setup from first principles — they want to start from something sensible and adjust.
What a template can be a starting point for
| Template kind | What it sets up |
|---|---|
| Workspace setups | How a new workspace is arranged — the smart starting point for a team's whole TimeCampus configuration |
| Project setups | A ready-made project structure — categories, tasks, and billing conventions for a kind of engagement |
| Workflow starting points | Pre-built workflow rules — common automations you adopt rather than author |
A team lead packaging their team's proven setup as a template — so the next team starts where this one ended up — is exactly the use the template model exists for.
The Templates page
Open Templates in the app at app.timecampus.com to browse what's available. The surface has three steps:
- Browse — the Templates page lists the available templates
- Inspect — open a template's detail view (Templates → detail) to see what it contains and what applying it will set up
- Apply — run the apply flow (Templates → apply), which walks you through bringing the template's setup into your workspace
Applying a template is additive scaffolding, not a lock-in: once applied, everything it set up is yours to reconfigure like anything you'd built by hand.
Templates and access control
Templates operate within the same boundaries as everything else:
- Applying a template only sets up things your role could create yourself — see Access control
- Template contents are workspace-scoped; a template can't reach outside your workspace
What works today vs. what's rolling out
The Templates page, the template detail view, and the apply flow are part of the app surface today.
The template engine — a persisted template catalog, template application that actually materialises setups into your workspace, and publishing your own workspace setup as a template for others — is still being built. Today the Templates surfaces are UI: you can see how browse → detail → apply will work, but applying a template doesn't yet change your workspace's data. Smart workspace templates — where the platform suggests setups based on how you work — follow as part of the AI-assisted direction on the roadmap.
Templates vs. Industry Solutions
Templates and Industry Solutions are related but different in scope:
| Templates | Industry Solutions | |
|---|---|---|
| Scope | One setup — a workspace, project, or workflow starting point | A curated bundle for a whole field |
| Audience | Anyone starting something new | Teams in a specific industry (consulting, creative, technology, education) |
| Granularity | Apply one, adjust, move on | A broader accelerator across your setup |
Next steps
- Industry solutions — field-specific curated bundles
- First workspace — what a workspace template gives you a head start on
- Workflows — the automations templates can pre-package