Yes. If you need to create the same custom role once and use it for many new customer tenants, use a Workspace template. A template lets an MSP admin choose an MSP-wide custom role as the default role for new tenants created from that template, so the role does not need to be recreated tenant by tenant.

Tenant templates are useful when you repeatedly onboard tenants with the same starting configuration: package, default invite role, AI settings, Workshop items, security settings, model access, and integration/tool access defaults.

When to use tenant templates

You onboard many tenants with the same role setup. For example, every new tenant should start with a limited "Technician" or "Read Only" custom role.
You want invite links to assign a consistent default role. The template's default role can seed the new tenant's invite-link role during tenant creation.
You want the same Workshop starting point. Templates can include selected workflows, apps, and agents that should be available to the new tenant.
You want safer defaults for AI, models, integrations, and tools. A template can set day-one access defaults that tenant admins can review after creation.

What a template can apply

A Workspace template can apply these settings when a new tenant is created:

Package setting for the tenant creation flow, when a package is configured on the template.
Default role, using either a built-in tenant role or an MSP-wide custom role.
Invite-link default role when invite links are enabled during tenant creation and the template has a default role.
AI settings, including Auto LLM behavior, memory, personalization, subagents, artifact settings, and the default model where those controls are available.
Blocked models and other model-access defaults where model-access controls are available.
Security and access settings, including MFA requirement, beta features, and community Workshop access.
Workshop content, including selected workflows, apps, and agents.
Integration and tool defaults, including available integrations, built-in tools, and Custom MCP creation/use defaults where those controls are available.

Template settings apply when the tenant is created. Editing a template later does not retroactively update tenants that already exist.

How role reuse works

For reusable roles, create or choose an MSP-wide custom role from the template role section. Then set that role as the template's default role. New tenants created from the template start with that role available, and invite links can use it as the default signup role.

This is different from creating a custom role inside one existing tenant. A tenant-specific role belongs to that tenant and is not automatically copied into every other tenant. If you want the same role available across many new tenants, create it from the Workspace template flow or choose an MSP-wide custom role that already appears in the template's Custom roles section.

Create a template with a reusable custom role

Open the Admin Dashboard.
Go to Workshop, then Templates.
Choose Create new, enter a template name and description, and select any workflows, apps, or agents that should be included for new tenants.
Select Continue to open the template settings.
In Standard roles, choose a built-in default role if you want the template to use one of the built-in tenant roles.
In Custom roles, choose an existing custom role or select Add new to create the reusable custom role.
Select the role so it becomes the template's default role.
Configure the package, AI settings, security settings, model settings, and other defaults you want the tenant to start with.
If the Integrations & Tools step appears, choose Continue, set the integration/tool defaults, then choose Publish template.
If your workspace does not show a separate Integrations & Tools step, choose Publish template from the settings page.

Use the template when creating a tenant

After a template is published, use it when creating tenants:

Single tenant creation: choose the template in the tenant creation flow when the template option is available. The new tenant receives the template's starting settings.
Bulk tenant creation: use the in-product sample CSV. When templates are available, the sample CSV includes a Template column. Use the template value from the downloaded sample CSV, especially if a template was just created or renamed.
Default template: if a template is marked as the default template, it can be used for new tenants when no specific template is chosen.

If you enable invite links while creating the tenant and the selected template has a default role, that default role is used for the invite link. If the template does not have a default role, you still need to choose a valid default invite role in the tenant creation or CSV flow.

What templates do not do

They do not update existing tenants. Templates apply only at tenant creation time.
They do not turn every tenant-specific role into a reusable role. Use an MSP-wide custom role for repeatable onboarding across new tenants.
They do not override global policy. Organization-wide policy still applies, and anything denied globally cannot be enabled by a template.
They do not change users who already joined. Changing a template or a tenant's invite-link default role affects future tenant creation or future signups, not users who already have a role.
They do not guarantee integrations are already connected. Templates can set access defaults, but users may still need to connect or authorize integrations depending on the integration.

Troubleshooting

I created a custom role in one tenant. Why can't I select it in the template?
Tenant-specific roles belong to that tenant. To reuse a role across many new tenants, create the role from the Workspace template's Custom roles section or use an MSP-wide custom role that appears there.

The new tenant did not use the role I expected.
Confirm the tenant was created from the intended template, confirm the template has the expected default role selected, and confirm invite links were enabled if you expected the invite link to use that role.

The CSV says the template is unknown.
Download a fresh in-product sample CSV after the template has been published, then copy the Template value from that sample into your upload file. The upload must match the template value expected by the bulk-create flow.

I changed a template but an existing tenant did not change.
That is expected. Templates are creation-time defaults. Update the existing tenant's settings directly if that tenant already exists.

An integration or model is locked in the template editor.
It is likely restricted by organization-wide policy. Template defaults can add starting restrictions for new tenants, but they cannot override global policy.

Tenant Templates: Reuse Roles and Settings for New Tenants