Evose

Security and access

Data and tools, granted by permission

From organization roles to API keys, five layers decide who can use which agent, read which documents and call which tool.

Contact sales

The same workspace seen as three members: the agents they can use and at what level, the knowledge folders they can see and the tools they can call all differ.

Five layers of permissions

From the organization down to each call, every layer can be tightened on its own.

  1. 1

    Organization roles

    A built-in admin and custom roles, set by module, page and button

    • Admin
    • Security auditor
    • Custom role
  2. 2

    Workspace roles

    Apps, data, capabilities and workspace admin, set separately

    • Workspace admin
    • Builder
    • Member
  3. 3

    Resource grants

    Agents, workflows, knowledge bases, tools and skills, each granted on its own

    • Use
    • Observe
    • Edit
    • Manage
  4. 4

    Project access

    Applies to members of your organization only

    • Can use
    • Can edit
    • Can manage
  5. 5

    API key scopes

    Limit who a key belongs to and which apps it can call

    • Owner scope
    • Callable apps

Every resource, granted on its own

Grant members or member groups one of four levels: use, observe, edit or manage.

ResourceGroup · Frontline supportGroup · RiskSarah Mitchell
Account assistantUseObserveManage
Document pre-checkUseEditManage
Account openingUseUseManage
Core systemUse—Manage

Who sees what, and uses what,is the organization's call

Knowledge permissioned by folder

Lists, search and file reads all follow what each member can actually see.

Sign-in and members

  • Several ways to sign in

    Email codes, SSO and Lark, each turned on or off on its own

  • Email domain allowlist

    Only addresses on your domains can sign in with an email code

  • Org chart sync

    Sync departments and members from Lark, by hand or on a schedule

  • Offboarding in bulk

    Up to 1,000 people at a time, with their workspace access turned off too

Credentials, kept apart

Admins define secrets and grant them by workspace and app. The interface only shows whether one is set.

FAQ

Plan your rollout with us

Tell us about your teams and where Evose should run.

Contact sales