Organizations

Agent > Organizations shows end users grouped by the organization_id attribute. There's no separate organization entity behind this: it's a GROUP BY over that attribute, so an organization only shows up once at least one of its members has identified with it set.

The list

Each row shows:

• Organization: the organization_name attribute when one has arrived, with the raw organization_id under it. Send no name and the id is all there is to show.
• Members: how many distinct users carry this organization_id.
• Last seen: relative time across all members, or "Never".
• Origin(s): which verified origins its members' sessions have come from.

Switch between Live and Test key tiers with the tabs above the table. There's no attribute-filter builder here, unlike Users.

Searching, sorting and paging

• Search with the box next to the tier tabs. It matches the organization id and the organization name.
• Sort by clicking Organization, Members or Last seen. Clicking again reverses the order, and a third click returns to the default of most recently seen first.
• Page with the controls under the table, which say which rows of how many you are looking at and let you show 10, 25, 50 or 100 rows at a time.

All three run on the server, so they cover every matching account rather than only the rows on screen. Any change that narrows or reorders the list returns you to page 1.

If nothing shows up: "Once identify() sends an organization_id attribute, accounts will show up here."

Naming an account

arcy.identify("user_123", {
  organization_id: "org_acme",
  organization_name: "Acme Inc",
})

Every organization_-prefixed attribute rolls up to the account, taking the value from the most recently seen member that sent it.

The detail page

Click a row to open that organization's page. Identity and attributes sit side by side in one row, with the member and session tables underneath. It shows:

• The header: the account name, its id, how many members it has, and how many sessions the selected key tier holds.
• Attributes: the account-level attribute bag rolled up from its members, labelled from your attribute registry. If nothing has arrived yet: "No organization-level attributes arrived for this account yet."
• Members: every user carrying this organization_id, with their email and user id, each linking to their own Users detail page. Searchable by name, email or id, sortable on every column, and paged ten rows at a time.
• Sessions: a combined table across every member, one row per session, showing which member it belongs to, its origin, the entry route the session started on, when it started, and the identity-verification outcome. Every column sorts, and the table pages ten rows at a time.

The Live/Test switch applies to the whole page, which is why the sessions themselves carry no key tier column.

There's no export on either page.

See also

• Attributes: declaring organization_id and other attributes
• Users: the same underlying data, one row per user instead of per account