Skip to content

    For workspace owners and IT

    Configure access, sign-in and action oversight

    Build roles from individual permissions. Connect one corporate identity provider through SAML 2.0 or OIDC. The audit log records actions and IP addresses, and administrators can end active sessions.

    Roles and permissionsSSOAudit log and sessionsWorkspace isolation
    app.teamevo.co/main/admin/access
    7Kate Ellis

    Roles and scope of access

    AdministratorThe entire workspace2
    HR partnerPeople, learning, surveys5
    ManagerTheir own team18
    EmployeeTheir own data and shared content209

    Audit log and sessions

    Kate E. changed the permissions of the HR partner roletoday, 11:04 · 93.80.•••.24
    Active sessions2
    Chrome · 93.80.•••.24

    Administration

    Four areas of control

    Settings are grouped by task: user permissions, corporate sign-in, audit log and sessions, and integration access.

    01

    Roles and granular permissions

    Build each role from separate permissions for publishing, moderation, analytics and workspace settings.

    • HR opens reports
    • Editors publish news
    • IT manages sign-in

    02

    Corporate sign-in

    Connect one corporate identity provider using SAML 2.0 or OIDC. After testing, require SSO and create users on their first sign-in.

    • Your company's IdP
    • SAML 2.0 or OIDC
    • Mandatory SSO

    03

    Audit log and sessions

    Review administrative events with the author, time and IP address. Open active user sessions and end a selected session.

    • Author, time and IP
    • Active sessions
    • Forced sign-out

    04

    Keys for integrations

    Issue a separate key for each data exchange and revoke it without interrupting other connections.

    • Employee import
    • Absence data from an HRIS
    • External calculation data

    Launch preparation

    Review access before inviting employees

    This sequence separates portal setup from IT, security and legal requirements.

    1. 01

      Assign a workspace owner

      The owner manages administrators and key settings. Separate roles can handle day-to-day work.

    2. 02

      Separate operational roles

      Give HR, editors, managers and IT only the sections and actions they need.

    3. 03

      Connect corporate sign-in

      Test SSO with a small group, then disable sign-in with a separate password.

    4. 04

      Review the log, sessions and documents

      Before launch, agree on logged events, audit-log access, active-session management, the SLA and data documents.

    Data residency in the EU/EEA

    SSO secrets are encrypted

    Roles control access

    Review materials

    Documents and settings for IT, security and legal

    Start with the public documents, then review roles, the audit log and integrations in a test workspace.

    Administrator workflow

    Questions about portal administration

    Roles, a change log and a clear administration layer that shows who publishes content, changes settings and manages access.

    Review roles and SSO in a test workspace

    Create a portal, configure separate roles for HR, editors and IT, then review the audit log and active sessions.