Templates
A template stands for a use case, for example project, department or internal team. It defines who can use it to create Teams or SharePoint sites, how they are set up and which rules apply to usage and lifecycle.
Templates always belong to an organisation. So first set up an organisation.
In all examples, we create the template Project in the organisation Contoso for projects with customers and external guests. Teams created from this template are later named, for example, 260215.001 - Project Atlas.
The settings
A template is split into tabs. Each tab has its own page:
| Page | Content |
|---|---|
| Template | Create the template: name, description, identifier, availability and audience |
| Approval | Whether and by whom requests are approved |
| Group | Team, sensitivity label, visibility, guest access, owners and members |
| Naming convention | Custom fields and rules for display name, email address and site URL |
| Libraries | Document libraries, folders and files |
| Channels | Channels, channel types and content |
| SharePoint | Property bag, site permissions, sharing and download |
| Lifecycle | When a team must be reviewed |
| Archiving | What happens on archiving |
| App | Permissions in the Seamless app and in Microsoft Teams |
See also
- How Seamless works
- Create a new team from the users' perspective