ISMS Copilot
Workspaces

How to use workspace personas for different compliance roles

Workspace personas let you set a default professional role for every conversation inside a workspace. Instead of selecting a persona each time you start a chat, you assign one to the workspace itself—so all conversations automatically use the right tone, focus, and depth for that type of work.

This is especially useful for consultants managing multiple client workspaces, teams separating audit prep from implementation, or anyone who wants consistent AI behavior across related conversations.

Available Personas

ISMS Copilot offers four personas. Each draws from the same compliance knowledge base but adjusts how information is presented.

Default

General-purpose, balanced responses. The AI covers topics broadly without assuming a specific role. Suitable for learning, exploring frameworks, or handling mixed tasks that span multiple disciplines.

Implementer

Focused on hands-on execution. Responses emphasize step-by-step guidance, control deployment, procedure writing, and practical actions. The AI assumes you are building or maintaining an ISMS and need actionable instructions.

Typical output: Implementation checklists, procedure drafts, configuration steps, control mapping tables.

Auditor

Focused on verification and assessment. Responses emphasize evidence review, gap analysis, audit findings, and conformity assessment against framework requirements. The AI assumes you need to evaluate whether controls are effective and properly documented.

Typical output: Audit checklists, evidence requirements, nonconformity descriptions, sampling guidance.

Consultant

Focused on advisory and strategy. Responses emphasize risk-based prioritization, strategic recommendations, client-facing deliverables, and business context. The AI assumes you are advising an organization and need outputs suitable for stakeholder communication.

Typical output: Gap assessment summaries, roadmaps, executive briefings, maturity scorecards.

Setting a Workspace Persona

During workspace creation

  1. Open chat.ismscopilot.com and navigate to the Workspaces page or click the + button in the sidebar.

  2. Enter a workspace name (e.g., "Acme Corp - ISO 27001 Implementation").

  3. Select a persona from the Default Persona dropdown: Default, Implementer, Auditor, or Consultant.

  4. Click "Create Workspace".

Every conversation you start inside this workspace will automatically use the persona you selected.

Changing the persona later

  1. Go to the Workspaces page ("View all workspaces").

  2. Click "Edit" on the workspace card.

  3. Change the persona in the dropdown.

  4. Click "Save Changes".

The updated persona applies to new messages going forward. Previous responses in existing conversations are not retroactively changed.

Name your workspaces to reflect both the project and the role. For example, "Client X - Audit Prep" with the Auditor persona, or "Internal ISMS Build" with the Implementer persona. This makes it obvious at a glance what kind of work belongs there.

When to Use Each Persona

Implementer

  • Building your ISMS from scratch—drafting policies, defining scope, creating the risk assessment methodology

  • Deploying Annex A controls and writing supporting procedures

  • Creating operational documents like access control procedures, incident response plans, or backup schedules

  • Configuring compliance tooling and mapping controls across frameworks

Auditor

  • Preparing for a Stage 1 or Stage 2 certification audit

  • Running an internal audit program—planning, sampling, writing findings

  • Reviewing evidence packages to confirm they meet ISO 27001, SOC 2, or other framework requirements

  • Conducting gap analysis against a target framework

Consultant

  • Managing multiple client compliance projects from a single account

  • Creating assessment reports, maturity models, or remediation roadmaps for clients

  • Providing strategic advisory on framework selection, risk prioritization, or budget allocation

  • Preparing executive-level summaries and board presentations

Default

  • General compliance questions or learning about a new framework

  • Mixed tasks that span implementation, audit, and advisory in a single conversation

  • Quick lookups on control definitions, clause references, or terminology

Personas vs. Standalone Persona Selection

ISMS Copilot provides two ways to use personas, but they are mutually exclusive:

  • Workspace persona — set at the workspace level, applies automatically to all conversations in that workspace.

  • Standalone persona — selected from the chat input dropdown when you are not inside a workspace.

You cannot use both at the same time. Here is what happens if you try:

  • If you select a persona while inside a workspace: A dialog appears warning "Personas not compatible with workspaces, persona will reset to Default." Your workspace selection is cleared.

  • If you select a workspace while a standalone persona is active: The persona resets to the workspace's default persona, and your standalone selection is cleared.

Switching between a standalone persona and a workspace always triggers a reset. If you need a specific persona for a specific project, set it as the workspace default rather than toggling manually. This avoids accidentally losing your workspace context.

Rule of thumb: Use workspace personas when you have an ongoing project that consistently needs one role. Use standalone personas for quick, ad-hoc conversations outside of any project context.

Combining Personas with Project Instructions

Workspaces support custom instructions—free-text context that the AI reads before every response. When you pair a persona with project instructions, you get highly targeted responses without repeating yourself.

For example, a workspace configured with:

  • Persona: Implementer

  • Instructions: "We are a 50-person SaaS company pursuing ISO 27001 certification. Our scope covers the cloud platform and supporting corporate IT. We use AWS, Google Workspace, and Jira."

...will produce implementation guidance that is already tailored to your organization's size, scope, and tooling—without you needing to restate that context in every message.

Another example:

  • Persona: Consultant

  • Instructions: "Client is a Series B fintech company, 120 employees. They need SOC 2 Type II and are targeting a Q3 audit window. Primary gaps are in change management and access control."

This combination means every response is framed as advisory output appropriate for that specific client engagement.

Personas control how the AI responds (tone, structure, focus). Project instructions control what the AI knows about your context (organization, scope, constraints). Using both together produces the most relevant and consistent results.

Summary

PersonaBest forResponse style DefaultGeneral questions, learning, mixed tasksBalanced, broad ImplementerBuilding ISMS, deploying controls, writing proceduresStep-by-step, actionable AuditorAudit prep, evidence review, gap analysisEvaluative, evidence-focused ConsultantClient advisory, strategy, reportingStrategic, business-oriented

Set the persona at the workspace level for consistent behavior across all conversations in a project. Pair it with custom instructions for the best results.

Was this helpful?