# Participants hub Source: https://docs.settlemint.com/docs/operators/user-management/participants-hub The Participants hub helps operators review users, entities, identity registration status, KYC evidence, holdings, activity, and security signals. The **Participants** hub brings together the people and on-chain entities that can interact with assets on the platform. It helps operators review who has platform credentials, which identities and contract accounts are registered, and what evidence is available before taking an identity, KYC, or security action. The hub is split into three working areas: * **Users**: participants with platform credentials. The list shows each user's name, email, wallet address, participant type, linked identity address, and registration status. * **Entities**: participants without login credentials, such as assets, vaults, smart accounts, or other system identities. The list shows each entity's name, contract address, identity address, entity type, and registration status. * **Insights**: identity and claim activity metrics for administrators, identity managers, and claim issuers. The Users and Entities lists open a detail workspace when you select a row. ## Decide where to start [#decide-where-to-start] Start from the area that matches the record you need to review: | Need | Open | Confirm | | ------------------------------------------------------------------ | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Review a person with platform access | Participants > Users | Name, email, wallet, identity address, registration status, KYC state, holdings, security signals, and recent wallet activity. | | Review a contract, asset, vault, smart account, or system identity | Participants > Entities | Entity type, contract address, identity address, registration status, verification claims, data-feed state, and recent account activity. | | Check system-level identity and claim trends | Participants > Insights | Identity registrations and claim activity before opening a specific user or entity record. | ## Users list [#users-list] Go to **Participants** > **Users** to review participants with login credentials. The users table supports search, filters, export, and column visibility controls. A user can appear as an admin, trusted issuer, or investor based on their platform and on-chain roles. If your role can create users, the page also shows **Create user**. See [Create users](/docs/operators/user-management/create-users) for the direct account creation workflow. If you do not have permission to view users, the page shows an access-restricted state instead of the table. ## User detail workspace [#user-detail-workspace] Open a user from the table to review the user's participant record. The header shows the user's display name, participant type, registration status, wallet address, and identity address when available. The user detail workspace can include these cards and drill-down views: * **Basic info**: account details such as display name, email, wallet, identity address, and recent account activity. * **Security**: two-factor authentication and active-session information. This card is available to roles that can manage user security. For your own security settings, see [Account security](/docs/operators/user-management/account-security). * **Verifications**: identity claims associated with the user's on-chain identity. * **Information**: KYC profile status, approved name when available, pending-update state, and open action requests. * **Holdings**: assets held by the user's wallet. The card uses the selected user's wallet as its balance scope. It is available to platform administrators and to roles that can read users in the current organization when the wallet belongs to a user in that organization. A wallet outside the active organization remains restricted. * **Activity log**: recent blockchain activity for the user's wallet, with a full activity view for deeper review. The workspace can also show a setup checklist for identity and verification work. The checklist appears for identity and verification roles when the user still needs follow-up, such as identity registration, KYC verification, updated KYC information, or a re-issued KYC verification. ## Entities list [#entities-list] Go to **Participants** > **Entities** to review participants that do not log in as platform users. This includes on-chain identities linked to assets, vaults, smart accounts, contracts, wallets, or system actors. The entities table supports filters, export, and column visibility controls. It is sorted by recent activity by default. If you do not have permission to view entities, the page shows an access-restricted state instead of the table. ## Entity detail workspace [#entity-detail-workspace] Open an entity from the table to review its on-chain participant record. The header shows the entity name, registration status, contract address, and identity address when available. The entity detail workspace can include: * **Basic info**: identity and contract-account details. * **Verifications**: identity claims associated with the entity. * **Activity log**: recent blockchain activity for the entity's account, with a full activity view for deeper review. * **Data feeds**: feed configuration and publishing state for entities that participate in data-feed workflows. ## Activity log evidence [#activity-log-evidence] The activity log is the participant-level view of indexed blockchain events. It helps reviewers answer: what changed, when it changed, which transaction recorded it, and which account or contract was involved. Open **Activity log** from a user or entity detail workspace: 1. Select the participant from **Participants** > **Users** or **Participants** > **Entities**. 2. Confirm the workspace header shows the expected wallet, contract, or identity address. 3. Open **Activity log** to review the full event table. 4. Filter by event name or search for part of an event name when you need a narrower audit trail. 5. Open an event row when you need the sender, emitter, timestamp, block number, transaction hash, event parameters, and any decoded claim values. The activity scope depends on the participant type: | Participant detail page | Activity scope | | ----------------------- | ------------------------------------ | | User detail | The user's wallet address. | | Entity detail | The selected entity account address. | The table is backed by indexed events where the scoped address appears as the sender, account, contract, token, system, or an involved address. Supported list controls include event-name filtering, event-name search, timestamp-based sorting, pagination, and event-name facets. If your role cannot read the requested account's activity, the view returns an empty activity result instead of exposing another participant's events. Activity log evidence is useful for compliance review, incident investigation, and operational reconciliation. It does not replace the KYC evidence workflow. Use the KYC cards and verification views for identity documents, claim status, and approval or rejection history, then use the activity log to correlate later on-chain events for the same participant. Use the [webhook events reference](/docs/events) to check event names and payload schemas, and use [blockchain monitoring](/docs/developers/operations/blockchain-monitoring) when you need indexer or chain RPC health for the same period. ## Insights [#insights] Go to **Participants** > **Insights** to review identity and claim evidence across the current system. The page is available to administrators, identity managers, and claim issuers. The Insights page shows: * total identities created by the identity factory * active and pending identity registrations * current claim counts for issued, active, and revoked claims * identity growth and claim activity charts for the trailing 24 hours or trailing 7 days Use Insights when you need a system-level signal before opening an individual participant record. Use the Users or Entities workspaces when you need the evidence for one wallet, identity, contract account, or claim subject. ## Activity and audit evidence [#activity-and-audit-evidence] Participant evidence is split by review level: | Review level | Where to look | What you can confirm | | ------------------ | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | System trend | **Participants** > **Insights** | Identity creation, registration state, and claim activity trends. | | User record | **Participants** > **Users** > user detail | Wallet, identity address, KYC profile state, verification claims, holdings, and recent wallet activity. | | Entity record | **Participants** > **Entities** > entity detail | Contract or system identity details, verification claims, data-feed state, and recent account activity. | | Full activity view | **Activity log** from a user or entity detail page | Recent blockchain activity for the selected account. | Claims and activity shown in the participant workspaces are review evidence, not an automatic approval. If the evidence does not match the intended operating step, review the identity, KYC, or claim workflow before minting, transferring, or changing access. ## Permissions and access [#permissions-and-access] Participants views are permission-aware: | View or action | Required access in the app | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | Participants sidebar | Administrator, identity manager, or claim issuer. Administrators without participant-management permissions see disabled navigation items. | | Users list | Permission to read user records. | | Invitations tab | Organization owner or administrator. | | Create user action | Permission to create users, or organization owner or administrator access to manage invitations. | | Entities list | Permission to list entities. | | Entity detail workspace | Identity manager or claim issuer access. | | Insights | Administrator, identity manager, or claim issuer. | Opening the Participants hub does not grant every participant action. Creating users, registering identities, reviewing KYC evidence, and managing user security each depend on narrower permissions. When an action is unavailable, check that you are in the expected organization and that your account has the relevant identity, verification, or system-management role. ## Related guides [#related-guides] * [Account security](/docs/operators/user-management/account-security) * [Invite users](/docs/operators/user-management/invite-users) * [Create users](/docs/operators/user-management/create-users) * [Provide KYC data](/docs/operators/user-management/provide-kyc-data) * [Register user](/docs/operators/user-management/register-user) * [Manage KYC data](/docs/operators/compliance/manage-kyc-data) * [Verify KYC](/docs/operators/compliance/verify-kyc) * [Webhook events](/docs/events) * [Webhook endpoints](/docs/developers/api-integration/webhook-endpoints) * [Blockchain monitoring](/docs/developers/operations/blockchain-monitoring)