A template package bundles individual templates, such as Microsoft Teams, SharePoint sites, or Planner, into a complete project package. It serves as the foundation for automatically creating entire projects, including team structures, metadata, and permissions.
Prerequisites
Before you can create a template package, the following steps must be completed:
- Metadata has been created and activated.
- Naming conventions are defined and assigned to the templates.
- Individual templates (e.g., Project Team) are fully configured.
1) Navigation: Opening Template Packages
In the Teamsware admin area, locate the Templates and Packages block on the right-hand side and select the Template Packages menu item.
2) "All Template Packages" List
In the overview, you can see all existing template packages. You can choose between different views:
- Active (Gallery): The standard tile view.
- Active (List): A table view.
- Active (Projects only): Shows only packages capable of project creation.
- Disabled: Packages no longer in use that can be reactivated.
Use the + Add New Item button to create a new template package.
3) Creating a Template Package – Basic Data
Enter the basic information in the "Template Packages / Deployments" form:
- Title: A concise name, e.g., "Demo Project".
- Description: A brief explanation of the package's purpose and use case.
- Is a Project?: Select "Yes" if a full project should be generated.
- Active: Select "Yes" so the package can be used immediately.
4) Defining Details
Under the Details tab, define the specific contents of the package:
- Connected Templates: Select the previously created templates (e.g., Project Team including channels, folders, and Planner). You can link as many templates as needed.
- Metadata: Specify the metadata used in the naming conventions (e.g., Number, Location). These control the input prompts during project creation.
- Image: You can optionally upload an image for the gallery view.
5) Configuring Permissions
The Permissions tab determines who can approve the package and who can see it:
- Approved by: Persons required to authorize project creation. Users without approval rights can initiate a project request, but it will only be created after approval.
- Visible to: Defines the target audience. If left empty, all users can use the package.
- Workspaces visible to: Optionally restricts visibility to specific workspaces.
6) Saving
Finally, click Save. The template package is now ready for automated project creation.
Best Practices
- Unique Naming: Use clear naming schemes like "PR_[Number]_[ProjectName]".
- Precise Metadata: Ensure consistency so that all projects are created uniformly.
- Clean Up: Disable old packages to maintain a clear overview for users.
Common Errors & Solutions
| Problem | Solution |
|---|
| Package is not displayed | Check if the status is set to Active = Yes. |
| Metadata missing | Ensure all metadata is activated and linked to the templates. |
| Approval process not working | Verify that the correct persons are listed under "Approved by".
|