Resources · 3 min read
Roles and responsibilities
Understanding the different roles, permissions, and stakeholders involved in your Intric onboarding journey.
A successful Intric implementation depends on having the right people in the right roles. This article explains the platform roles, organizational stakeholders, and best practices for structuring your team during the onboarding process.
Overview
Section titled “Overview”Your Intric onboarding involves both platform roles (technical permissions within Intric) and organizational roles (how the initiative is anchored in your organization). Understanding both dimensions ensures smooth adoption and long-term success.
Platform Roles and Permissions
Section titled “Platform Roles and Permissions”Intric has three core platform roles, each with specific permissions:
| Role | Key Permissions | Responsibilities | Who Should Have This Role |
|---|---|---|---|
| Admin | Full platform oversight; user management; security settings; configure security classifications; manage AI model access; manage spaces and organizational structure | Oversee all aspects of the Intric environment and ensure proper configuration | A small, agile group—typically around three people—to drive the initial implementation |
| Creator | Build assistants; manage knowledge bases; create and share AI assistants; manage documents and integrations | Develop assistants that create value for themselves and colleagues | Individuals with good knowledge of their specific operations and a curious interest in AI. No technical background required |
| User | Access assistants; interact with AI tools; provide feedback | Use the platform to get work done and provide feedback on assistant effectiveness | End users across the organization who benefit from assistants created by others |
Best practice: Maintain a small, agile admin group—typically around three people—to drive the initial implementation.
Project Participants and Stakeholders
Section titled “Project Participants and Stakeholders”Understanding who is actively involved in the project versus who needs to be kept informed is crucial for successful implementation.
Project Participants
Section titled “Project Participants”These individuals are actively involved in building and implementing Intric:
| Role | Description |
|---|---|
| Project Leader | Leads the implementation project and coordinates activities |
| Admins in Intric | Manage the platform, configure settings, and support users |
| AI Ambassadors | Build assistants and drive adoption within their areas |
| AI Council | The strategic governance group that owns the AI initiative—typically the admin group together with IT and information security. See The AI Council |
| IT | Provide technical support and integration assistance |
| Information Security / Legal | Ensure compliance and approve security classifications |
Stakeholders
Section titled “Stakeholders”These individuals need to be informed and engaged but are not directly involved in day-to-day project work:
| Role | Description |
|---|---|
| Project Sponsor | Provides strategic direction and secures organizational mandate |
| Management/Leadership | Needs to be kept informed and ensures resources are available |
| Employees | End users who will benefit from and use the assistants |
| Customers (or Inhabitants) | External stakeholders who may be impacted by improved services |
Important distinction: Project participants actively do the work of implementing Intric, while stakeholders need to be kept informed to ensure the initiative has support and mandate.
Keeping Stakeholders Informed
Section titled “Keeping Stakeholders Informed”While stakeholders like management and leadership may not build assistants or participate in day-to-day project work, they play a vital role in ensuring success:
Management and Leadership:
- Provide strategic direction and mandate for the initiative
- Need to be kept informed about progress through regular updates
- Ensure the initiative has necessary resources and budget
- Support organizational change and remove barriers
Why this matters: A management team that’s informed and aligned will ensure the initiative has the mandate it needs, even if they don’t directly participate in building assistants. Regular communication prevents surprises and maintains support throughout the onboarding journey.
AI Ambassadors: The Engine of Adoption
Section titled “AI Ambassadors: The Engine of Adoption”AI Ambassadors are key individuals who bridge technology and operations—they build assistants, drive adoption within their areas, and share knowledge across the organization. No technical background is required; success comes from operational knowledge, curiosity about AI, and willingness to learn and teach others.
For a full overview of the role, responsibilities, and how to get involved, see The AI Ambassador.
Best Practices for Organizing Your Team
Section titled “Best Practices for Organizing Your Team”Small Admin Group
Section titled “Small Admin Group”Keep your admin group small and focused:
- Typically 3 people for most organizations
- Educate them thoroughly first
- They become your internal experts
- Can support creators and users
Your Role as Project Participant
Section titled “Your Role as Project Participant”If you’re part of the onboarding project, you can expect:
During Phase 1 (Implementation)
Section titled “During Phase 1 (Implementation)”- Participate in kick-off meeting
- Complete security classification setup (if relevant to your role)
- Attend admin or creator training
- Begin building or testing first assistants
During Phase 2 (Adoption)
Section titled “During Phase 2 (Adoption)”- Join Track 1: the AI Council if you are in the admin or governance group—regular strategic and governance check-ins
- Join Track 2: AI Labs with AI Ambassadors to test, learn, and build
- Draw on workshops or PT Sessions from the toolbox when they fit where you are
- Build and test assistants for your area
- Share learnings with colleagues
- Gradually scale usage across your team