Shared
Four screens in the Identity suite belong to no single EdgeKit product:
- Identity › Audience › Users lists every user your organization has, one row per person. See Users.
- Identity › Audience › Organizations lists your user organizations: the groups, such as a user’s employer, whose members share access through their seats. See User organizations.
- Identity › Audience › Grants lists every grant: who has access to which product, from when until when, and why. See Grants.
- Identity › Audience › Observability shows what happened to users, grants and profiles, newest first. See Observability.
Two meanings of organization
Section titled “Two meanings of organization”Your organization is the account EdgeKit opens for you: it owns your sites, your staff and your console. A user organization is a group of your users, for example a company and its employees. The Organizations screen in the Identity suite lists user organizations. Your own organization’s settings are elsewhere in the console.
Live data, not the draft
Section titled “Live data, not the draft”These screens show live data. A change you make here, such as a corrected email address or a new seat, takes effect at once, with no deploy. Configuration you author on other screens is different: it reaches requests only after a deploy (see Draft and deployed configuration).
Who can do what
Section titled “Who can do what”| Action | Roles |
|---|---|
| View Users, Organizations and Grants | Everyone in your organization |
| View Observability | Every built-in role: Owner, Admin, Developer, Editor, Member |
| Correct a user’s name or email address | Owner, Admin |
| Open a user organization, seat a member, change a role, add a domain | Owner, Admin |
Only the Owner and Admin roles can change anything on these screens. Anyone else can open them, and a change they try to save is refused.
Every staff read and change is recorded
Section titled “Every staff read and change is recorded”Each time the console reads or changes your organization’s data, users included, EdgeKit writes a record of it in your organization’s own database: who did it, when, and what was asked for. A screen writes a read record each time it loads its data. A change also writes its own record, which names what moved.
The record says which kind of access it was:
staff.readandstaff.write: a member of your organization in the console.support.readandsupport.write: EdgeKit staff, who are not members of your organization.
EdgeKit staff can read and change your organization’s data only while support access is on for your organization. While it is off, every EdgeKit staff read and change is refused, and your own staff are not affected. Any site’s screen in Delivery › Delivery › Sites shows the current value, read-only, under Configuration › Support access.
No console screen lists these records today.