Templafy Spaces is a powerful feature designed to enhance content efficiency and security within the Templafy platform. This guide aims to provide users with a clear understanding of what Spaces is and how to effectively work with this feature.
Prerequisites
|
What is Templafy Spaces?
Spaces is a suite of content library capabilities within Templafy that offers a structured and secure approach to content administration. It allows users to organize and manage their content in a way that aligns with their specific roles and responsibilities. The primary goal of Spaces is to streamline content distribution and management, ensuring that users have access to the right information at the right time.
Content Organization
Spaces divides the Templafy content library into sub-sections, each with its own provisions for content administration, user management, and folder structure. This hierarchical organization is particularly beneficial for companies operating in regulated or brand-conscious industries, where precise information silos are crucial.
Granular Content Permissions
One of the core features of Spaces is the implementation of granular content permissions. This ensures that users, especially Templafy Admins, only have access to the content relevant to their specific roles. By minimizing universal access rights, Spaces helps safeguard files from accidental or deliberate tampering, reducing organizational risk.
Spaces tab
The spaces section can be found within the admin center of your Templafy tenant.
Within this tab you can:
- View access for all Admin Center users
- Manage space owners and members
- Show and hide deactivated spaces
- Delete deactivated spaces
NoteDynamics compile will work across different Spaces. This means that a document can dynamically be generated utilizing content from multiple Spaces. End user with access to the Space hosting the dynamic document will get the document containing all content regardless of their access rights to the other Spaces. This allows for content to be continuously managed in a single place and need no duplication. Admins that are configuring overarching dynamic documents will need Space Owner access to all relevant Spaces in order to access the corresponding asset IDs. |
Comments
Article is closed for comments.