Skip to content

Blueprint

The Blueprint area of IMPACT 365 covers how your organization defines and maintains the building blocks used across workspaces and repositories: user roles, workspace templates, repository (list) templates, and taxonomy.

Managing user access

IMPACT 365 supports role-based access to the portal and its features. Roles are typically aligned to SharePoint groups on the IMPACT portal site.

  • Admin — Full access to configuration, templates, and workflow.
  • Business broker — Can approve or manage requests and access business data (e.g. workspace requests, provisioned workspaces) without full admin rights.

Role assignment (grant/revoke) can be driven by the workflow engine: when you add the right Resource and Operation to the workflow queue, the system updates the user’s membership in the appropriate portal groups. This allows you to automate role changes from HR, identity, or approval processes.

Workspace templates

Workspace templates define the structure and settings of new SharePoint sites (and optionally linked Microsoft Teams) when a workspace is provisioned.

  • Source — A template is created from an existing SharePoint site that has been set up the way you want (libraries, lists, pages, settings).
  • Storage — The template is stored in a standardized format so it can be applied repeatedly.
  • Lifecycle — Templates can be created, updated (re-generated from the source site), and removed. Versioning is supported so you can track which template version was used for each workspace.

When a user requests a workspace, they choose a template; provisioning then creates a new site from that template so every new workspace starts from the same standard.

Repository (list) templates

Repository templates define list and library structures (columns, content types, views) that can be applied to existing workspaces.

  • Source — A template is created from an existing list or library on a source site.
  • Storage — The template definition is stored so it can be applied to other sites.
  • Use — When a user requests a repository (list or library) on a workspace, provisioning applies the chosen template to create the list or library on that site.

This keeps document libraries and lists consistent across workspaces (e.g. same columns, content types, and default labels).

Taxonomy

IMPACT 365 can export selected term sets from the Microsoft 365 term store (e.g. to Excel) and store them in a designated library with metadata. This supports:

  • Documenting and sharing taxonomy with business users.
  • Backup or audit of term set structure.
  • Use of taxonomy metadata in templates and provisioning (e.g. Business Authority).

Taxonomy export is triggered via the workflow engine by submitting the appropriate Resource and Operation with the term group and term set identifiers.

How Blueprint fits in

Capability Purpose
User roles (grant/revoke) Automate who has Admin or Business Broker access on the portal.
Workspace templates (create/update/delete) Define and maintain the standard site layout and settings for new workspaces.
Repository templates (create/update) Define and maintain the standard list/library structure for new repositories.
Taxonomy export Capture and store term set definitions for governance and reuse.

All of these operations are available as workflow operations. To trigger them from your own process (e.g. Power Automate or a custom app), add the corresponding Resource and Operation to the workflow queue; see Adapter Registry.

Next: Workspace & Repository Provisioning — How requests become new workspaces and repositories.