Understanding Scopes

Learn how ContentPaul's scopes manage visibility and customization of templates, workflows, and tag categories across your organization.

In ContentPaul, templates, workflows, and tag categories can be assigned different scopes: System, Company, and Workspace. Each scope defines who can access and manage these elements, allowing organizations to balance standardization with customization.

System Scope

  • Definition: Templates, workflows, and tag categories under the System scope are pre-made by ContentPaul and provided to all users.
  • Purpose: They are used for standardized tasks or situations that are common across various projects and users.
  • Examples:
    • Templates: Generic templates for social media posts, which are applicable to all users.
    • Workflows: A basic workflow that automatically applies to all new items unless a specific workflow is chosen.
    • Tag Categories: A category with predefined tags for various digital media channels, universally available.

Company Scope

  • Definition: Elements within the Company scope are accessible across all workspaces within the organization. Unlike System scope, these can be created and edited by users in the company.
  • Purpose: This scope allows for the creation of standardized processes and resources that can be utilized across the entire company, ensuring consistency while allowing customization.
  • Examples:
    • Templates: Company-wide templates for internal documents, such as project plans or communication protocols.
    • Workflows: Standardized workflows for company-wide processes like approvals or HR procedures.
    • Tag Categories: Tag categories that apply to the entire company, such as those used for categorizing internal documentation or company-wide marketing strategies.

Workspace Scope

  • Definition: Workspace-scoped elements are only visible and accessible to users within a specific workspace.
  • Purpose: This scope is ideal for resources that need to be tailored to the specific needs of a project, department, or client, ensuring privacy and relevance.
  • Examples:
    • Templates: Custom templates for a particular client or project, such as branding guidelines or specialized reports.
    • Workflows: Project-specific workflows that cater to the unique steps and approvals required by a client or department.
    • Tag Categories: Tags that are only relevant within the context of a specific workspace, like tags used for tracking tasks within a single client project.

Practical Use Cases

  • System Scope: A digital marketing team uses system-provided templates for social media posts across all clients, ensuring a consistent approach.
  • Company Scope: A company-wide workflow for onboarding new employees is applied across all departments, ensuring consistency while allowing each department to make minor adjustments.
  • Workspace Scope: An agency working with multiple clients uses workspace-specific templates and workflows tailored to each client, ensuring that only the relevant team members have access to these resources. This prevents cross-client visibility and maintains confidentiality.

By understanding and utilizing these scopes effectively, organizations can ensure that their templates, workflows, and tag categories are both universally accessible where needed and customized for specific projects or clients.