Avatars
Person entities support Gravatar (default) or custom URL avatars for visual identification.
People
People are individual contributors in your organization. Each person entity represents a team member with their expertise, team affiliations, and contact information.
What Is a Person Entity?
Section titled “What Is a Person Entity?”A person entity captures who someone is in the context of your organization. It includes their role, the teams they belong to, and how to reach them. Person entities turn a simple directory into a navigable map of expertise and responsibility.
Every person entity has:
- A name (first and last)
- A job title or role
- An email address for contact
- Team memberships showing which teams they belong to
- An avatar for visual identification
- Optional links to profiles, calendars, or other resources
- Optional documentation for bios, onboarding notes, or role descriptions
Key Features
Section titled “Key Features”Team Memberships
Connect people to teams. A person can belong to multiple teams, and team cards automatically reflect membership.
User Account Linking
Link person cards to user accounts to connect login access with organizational context.
Person Properties
Section titled “Person Properties”Required properties:
- Name: The person’s display name (e.g., “Alex Johnson”, “Sam Rivera”)
- Email: Contact email address
Optional properties:
- Title: Job title or role (e.g., “Senior Engineer”, “Product Manager”)
- Teams: One or more teams this person belongs to
- Avatar: Profile image via Gravatar or custom URL
- Links: Quick-access URLs to LinkedIn, calendar, GitHub, or other profiles
- Documentation: Markdown files for bios, role descriptions, or onboarding guides
- Pinned: Whether the person appears at the top of lists
- Featured: Whether the person is highlighted in special views
Avatars
Section titled “Avatars”Person entities support two avatar modes:
Gravatar: Uses the person’s email address to fetch their Gravatar profile image. This is the default and requires no additional configuration. If the email is not registered with Gravatar, a default placeholder is displayed.
Custom URL: Use a direct URL to an image file. This is useful when your organization hosts profile photos internally or uses a service other than Gravatar.
Administrators can also configure OIDC auto-provisioning to automatically create person entities when users log in through your identity provider. See Single Sign-On for details.
Team Memberships
Section titled “Team Memberships”Team memberships connect people to the organizational structure. A person can belong to multiple teams, and each team displays its members on its entity card.
When you assign a person to a team:
- The person’s card shows the team count in its relationship indicators
- The team’s card updates to reflect the new member count
- The topology explorer shows the connection between person and team
- Search results include the team affiliation
To assign team memberships, use the entity creation or editing wizard. In the Organization step, select one or more teams from the Teams field.
Linking Person Cards to User Accounts
Section titled “Linking Person Cards to User Accounts”Person entities are separate from user accounts. A user account provides login access; a person entity provides organizational context.
Linking a person card to a user account connects these two concepts. When linked:
- The user’s profile page shows their person card information
- The person card can display the user’s last login time
- Administrators can see which users have person cards and which do not
To link a person card to a user account:
- Open your profile from the user menu
- Click “Link to Person Card”
- Select the person entity that represents you
- Save the link
When to Create a Person Entity
Section titled “When to Create a Person Entity”Create a person entity when:
-
Someone is part of a team: If a person belongs to one or more teams in your organization, create a person entity to show their team memberships.
-
Someone owns a landmark: If a person is responsible for a service, project, or resource, create a person entity so you can assign them as the owner.
-
You need to track expertise: If you want to know who to contact about a specific area, person entities with titles and team memberships make that discoverable.
-
You want a complete organizational map: Person entities fill in the “who” in your knowledge graph, connecting people to the work they do and the teams they belong to.
People in the User Interface
Section titled “People in the User Interface”Person entities appear throughout Legend:
- Dashboard: Person cards display alongside landmarks and teams in the main grid
- Search: Search for people by name, title, email, or team membership
- Filters: Filter the dashboard to show only people using the type filter
- Team cards: Team entity cards show member count and member avatars
- Topology: Visualize team memberships and ownership relationships
- Detail drawer: Click a person card to see full details, team memberships, and owned landmarks
People vs Other Entity Types
Section titled “People vs Other Entity Types”Understanding the distinction between entity types:
- Person: An individual contributor (the “who”)
- Team: An organizational unit that groups people together
- Landmark: Something in your organization that people work on or maintain (the “what”)
People belong to teams and can own landmarks. This creates a clear chain: team members own services, projects, and resources. When something goes wrong, you can trace from the landmark to its owner to the teams they belong to.