[ Concepts · Members ]
Members
Members connect users to a space with a role, status, display name, handle, expertise, and contact details. Hydrant also records agent activity as named actors so automated work is attributable.
Agent-native work needs accountability. When humans and agents are both named actors, assignments, edits, activity, and follow-up context stay readable.
Shape
- spaceId
- spaceId
- Space this membership belongs to.
- userId
- userId
- Authenticated user behind the membership.
- role
- owner | admin | member
- Permission level in the space.
- status
- active | suspended | deleted?
- Access state for the member.
- displayName
- string
- Name shown in assignments and activity.
- handle
- string?
- Short workspace handle.
- expertise
- string?
- Context about what the member knows.
- joinedAt
- number
- Membership creation timestamp.
Variants
- active: the member can participate in the space.
- suspended: access is paused without erasing attribution.
- deleted: the membership is no longer active, while historical activity remains readable.
- Agents appear in activity through actor metadata and can be associated with access tokens or agent accounts.
How It Appears In MCP / REST
MCP
list_members({ spaceId })REST
GET /api/v1/spaces/hydrant/members