Skip to main content

Best Practices for Arist Workspace Governance

This guide walks through the best practices for setting up your Arist workspace, from roles and Teams to delivery methods, integrations, and the organization-level settings that shape every course.

Platform access level: Org Admins and Managers. Organization-wide settings belong to Org Admins; Managers handle day-to-day work for teams they belong to, within the limits described below.


Getting the most from Arist starts with a clear view of what your organization wants to achieve and who needs to be involved. Use those priorities to shape how you organize teams, maintain learner information, and manage access and settings.

series intro animation, Claude Design, same style as the other hub intros: inside the organization frame, Access, Learner records, Delivery and Shared content appear in turn and connect, ending on the line Getting the most from your workspace

1. Help people do their work with the right access

Decide who needs to create, deliver, analyze, or manage work before choosing their roles.

Teammates and learners

Teammates run Arist. Learners receive content and have separate learner records. Decide whether someone needs platform access, a learner record, or both before adding them. See Viewing and Managing Learners for learner records.

Choosing roles

Give each teammate the narrowest set of roles that covers their work.

  • Arist has five roles: Org Admin, Manager, Writer, Distributor, and Analyst.

  • A teammate can hold more than one role, but a Manager already has the Writer, Distributor, and Analyst capabilities.

See Managing Users and Roles for role definitions and teammate-access procedures.

Who can manage access

  • Org Admins manage teammate access across the organization.

  • Managers can invite teammates to teams they belong to and assign roles within their permissions.

  • Only Org Admins can add or remove teammates on the Default team.

Note: Managers can edit their teammates' roles, with limits. Only an Org Admin can grant the Org Admin role, change the roles of a teammate who already holds it, or change the roles of a teammate who belongs to more than one team. No one can change their own roles, whatever role they hold. Managing Users and Roles covers each limit.

Reviewing access

Agree who authorizes new access and who reviews it when responsibilities change.

  • Org Admins can download the organization’s teammate roster to compare roles and teams with current responsibilities.

  • Use Last login as sign-in information, not proof of recent activity or employment status.

  • Review pending invitations and revoke any that are no longer needed.


2. Make your workspace easy to navigate

Start with how groups work together, and give each team a clear purpose.

Teams and ownership

Org Admins create and delete teams; Managers maintain the teams they belong to.

current Team settings > Team details with team identity, name, description, Save, and the complete current Team settings navigation visible; Team details circled

Use teams where groups need to work with their own content, learners, and settings. Name a Manager responsible for each team’s day-to-day upkeep.

Plan where content should be managed and which team is responsible for it. The lists you work in follow the team selected at the top of the sidebar. The Default team includes every learner, so consider that organization-wide view when deciding who needs membership there.

Review team assignments when people change responsibilities. Removing a teammate from one team keeps their organization account; only an Org Admin can remove their organization access. For team details, membership, rules, and delivery options, see Managing Team Settings.

Folders and naming

Org Admins, Managers, and Writers can organize content into folders within the selected team. Only Org Admins can move content between teams.

current Content page with selected safe example team, full navigation, Folders row and existing named folders visible; one circle on Folders

Agree a simple folder structure and naming convention across teams, then use folders within each team to group related content by initiative, topic, or audience. A folder can hold courses, nudges, and surveys together.

Name someone on each team to keep its folders and content organized. See Finding and Managing Your Content for creating folders and moving content.


3. Plan how learner records stay up to date

If your organization has a learner-data integration, routine updates run automatically once it is configured. Without one, establish a process for keeping records current as employees join, move, and leave.

Org Admins and Managers can add, upload, and edit learners within the teams they can access. Org Admins define organization-wide metadata fields; Managers can update learner values in existing fields. See Viewing and Managing Learners for profile and import steps and Managing Metadata Fields for field definitions.

When an integration maintains learner records

Your IT team and Arist’s technical team work together during setup to agree which people and fields are included and how changes and departures should be handled. Once configured, the integration maintains those records automatically, without routine uploads or manual updates. Section 5 covers integration planning.

Metadata updates can change membership of rule-based teams and cohorts. Include these rules, active enrollments, and your organization’s offboarding and retention requirements in setup so the integration follows the agreed process.

When you use uploads or manual updates

Without an integration maintaining learner records, name an owner and agree which employee records are your source of truth. Decide who receives information about new starters, changes in responsibilities, and departures, and who uses it to update Arist.

Agree a review rhythm that suits how often your workforce changes. Reconcile Arist’s learner roster with current employee records, checking contact details, metadata, team and cohort membership, and people who have left the company. Review rule-based teams and cohorts before changing metadata they rely on. An Inactive delivery-method badge describes the delivery connection, not employment status.

Handling departures without an integration

Agree with an Org Admin who handles departures in Arist and which records your organization needs to retain. Include active enrollments and deliveries in that review, then follow your organization’s offboarding and retention policy when choosing an action. Removing a teammate’s platform access and managing their learner record are separate responsibilities.


4. Make content easy to receive and recognize

Choose delivery methods your audience can use and senders they will recognize.

Before changing a team’s delivery options, review the schedules that use them. The task guides explain the dependencies and the controls available for existing schedules.

Delivery methods

Org Admins enable delivery methods and manage their organization-wide configuration. Org Admins and Managers choose which enabled methods their teams use. Arist supports SMS, WhatsApp, Email, Microsoft Teams, Slack, and Arist Messenger.

Agree which methods suit your audience, who maintains the required addresses or connections, and who checks readiness before a first send. A schedule can use only a method enabled for its team. For organization and team configuration, see Using Delivery Methods and Configuring Delivery Methods in Settings.

Channels

Channels are named senders with their own name and image. Org Admins create and manage them; Managers choose which existing channels their teams can use.

Agree a recognizable name and purpose for each sender so learners know which stream of content they are receiving. Your organization can create up to eight channels; contact your Customer Success Manager if you need more. See Managing Channels for supported delivery methods and channel management.


5. Connect your systems to reduce repeated work

Work with Arist’s technical team and your IT team to set up automatic data flows between your systems and Arist.

An Org Admin should bring together the organization’s data owner, IT team, and Arist’s Technical Solutions Engineer during setup. Managers can contribute their teams’ learner-data requirements. A platform role alone does not configure a connection to another system.

The implementation teams agree, configure, and test each connection’s scope:

  • Learner data: Which system supplies each field, which people are included, and how records are matched.

  • Updates and departures: Which changes sync, how often, and what happens when a person leaves, including relevant enrollment and retention requirements.

  • Outbound records: Whether completions or other course data are sent to another system, and which records are included.

  • Technical maintenance: Who monitors errors and handles changes to fields, credentials, or the connected system. Arist’s technical team monitors and maintains Arist-managed integrations in partnership with your IT team.

Once configured, routine updates within that scope run automatically. Delivery through Microsoft Teams or Slack and synchronization of employee data are separate capabilities; using a delivery channel alone does not mean learner records are maintained automatically.

For discovery, configuration, and testing of a data integration, contact your Customer Success Manager or [email protected].


6. Give teams a consistent starting point

Set organization-wide defaults around your audience, language, brand, and support needs. Review them when those needs change.

Only Org Admins can change Organization settings. Managers should raise organization-wide changes with an Org Admin and manage their own team settings within their permissions.

the current Organization page with Organization selected in the full Settings navigation, organization defaults, Citation style where enabled, and all Options visible

Give each shared setting an owner who understands how teams use it. Before changing a default, check which teams, content, or learner workflows depend on it so a useful update does not disrupt their work.

Organization defaults and branding

  • Organization defaults: Org Admins maintain the organization’s name, logo, timezone, default language and content type. Where citations are enabled, they also choose the shared citation style.

  • Learner requirements and enrollment controls: Org Admins maintain learner email and import delivery-address requirements, the active-enrollment limit, and learner self-management options. Review these against your delivery and learner-data practices. See Managing Organization Settings.

  • Branding: Org Admins maintain organization-level branding. Agree which identity learners should see and coordinate channel names and images with it. Some branding is configured outside the Organization page; see Managing Organization Settings for the boundaries.

Content and language guidance

  • Translation instructions: Org Admins maintain language-specific terminology and translation guidance. Agree who supplies approved terminology and keeps it current. See Setting Up Translation Instructions.

  • Content guidelines and image generation: Org Admins manage the available organization-wide guidance and image settings. Name a content owner to maintain the voice, terminology, visual guidance, and logo choices your teams should follow. See Setting Up Content Guidelines and Configuring Image Generation.

Learner data and messages

  • Metadata fields and tags: Org Admins maintain field definitions and the organization’s tags. Agree names and intended uses before adding them, and check dependencies before removing a field. Managers maintain learner values through the learner tools; changing a value is different from changing the field itself. See Managing Metadata Fields and Managing Tags.

  • Response reminders and system messages: Org Admins maintain shared reminder intervals and message wording. Review the wording in every language you deliver in, including your learner-support contact. A schedule’s reminder choice is separate from the shared timing and text. See Configuring Response Reminders and Managing System Messages.

Note: Every control on this list applies to the whole organization. Org Admins own that level. If you are a Manager, ask an Org Admin for a change here. Your own team's settings are yours to run within your permissions.


7. Help teams build on useful shared content

Agree who maintains shared templates and how teams flag content that needs updating. See Managing Your Organization’s Template Library for organizing the shared library, assigning owners, reviewing content, and managing updates or archives, and Using Templates from the Content Library for reusing a template.


8. Keep the workspace working as your organization changes

Agree who reviews access and configuration when people join, move, or leave, when your data sources change, and when a team’s responsibilities change.

Org Admins can review organization-wide teammate Activity and the Security log. Managers can review Activity for teams they belong to. Use the record that matches the question you need to answer.

Name someone to check each change and follow up on anything that needs correcting.

Teammate activity

Teammate Activity helps you understand invitations, role changes, team membership, and removals. Earlier changes may not appear, so it is not a complete access history. See Managing Users and Roles and Managing Team Settings.

Security log

The Security log records supported create and update events and can show the fields that changed. It records changes rather than page views or report access. Use it to investigate recorded configuration changes; see Reviewing the Security Log.


Related articles

Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].

Did this answer your question?