Skip to content

Identity

Identity is where your organization’s users live. A user is one identified person. Until someone signs in, EdgeKit keeps anonymous state for their browser as a device, and anonymous browsing never creates a user.

Each organization has its own sign-in instance and its own database, and shares neither with any other organization. A person who uses two organizations’ sites is two unrelated users, one in each.

  • EdgeKit ID signs users in on your own domain, collects the traits you ask them for, and can run beside an identity provider you already have. See EdgeKit ID.
  • EdgeKit Profile derives one document per user and site from what EdgeKit holds about them, for your rules and your other systems to read. See Profile.

All six screens sit in the Audience group of the Identity suite:

Screen What it holds Documented in
Users One row per person, with their sites, organizations and grants Shared
Organizations User organizations: groups of users who share access through their seats Shared
Grants Every stored fact that a user or a user organization has access to a product Shared
Traits The questions you ask a user about themselves EdgeKit ID
Profile The fields EdgeKit derives for each user and site Profile
Observability What happened to users, grants and profiles, newest first Shared

The first screen is Identity › Audience › Users. Users, user organizations and grants belong to no single EdgeKit product, so their screens are described in Shared.

Your organization has one user row per person, across all of its sites. Each email address belongs to at most one user. A site records that a user has been seen there; it does not split them into a second user, and it does not limit what they can reach. See Users.

Access is a grant: a stored fact that one user, or one user organization, has access to a product. A member of a user organization reaches the organization’s grants through their seat. Grants carry no price. See Grants.