Skip to content
Riptides Docs

Users

The Users screen lists the people who drive agents in Riptides. These are the humans you scope a policy to when you want a rule to apply only to a specific person. In an access policy, a user is the actor: the human on whose behalf an agent is acting.

Open it from Agentic → Users in the sidebar.

Where users come from

Section titled “Where users come from”

Users can come from an identity provider you connect to Riptides (for example GitHub, Google, Microsoft Entra, or a generic OIDC provider). When someone signs in, they appear here with the details their provider supplies. They can also be added manually. To set up identity-provider sign-in, see OIDC and Identity Provider Setup.

Each user carries a SPIFFE ID, a stable identity Riptides assigns them. That identity is the link that lets a policy target one specific person: when an agent runs on someone’s behalf, Riptides attributes the activity to their identity, and a user-scoped policy matches on it.

What you see

Section titled “What you see”

Four cards summarize the directory: Total users, Active (30d), With SPIFFE ID, and With groups.

The table lists each user with:

  • User: name and email.
  • Provider: the identity provider they signed in through (used as a filter), when applicable.
  • SPIFFE ID: the identity assigned to them, or a dash if none.
  • Last login: when they last signed in.

Search by name or email, and filter by provider.

How users are used in policy

Section titled “How users are used in policy”

A policy can either govern an agent regardless of who is driving it or apply only when a specific user is driving it. The second case is exactly where this screen matters: when you restrict a workload to specific users in Access Control, you pick those people from this list. The Activity Monitor also shows the user behind each session, so you can see who ran which agent.

Next steps

Section titled “Next steps”