Skip to main content

Person or Group Column

The Person or Group column stores actual people - validated accounts from your organization directory - instead of typed names. Users pick from a people picker that suggests matches as they type, so Assigned To, Approver, and Owner fields always resolve to a real account with a photo, profile, and email address. That connection is what makes it powerful: views can filter to the current user with [Me], automations know exactly who to notify, and SharePoint uses the same column type for its built-in Created By and Modified By columns.
Related Features
Audience Targeting, Lookup Column, Site Members, System Columns

Common Use Cases

  • Task assignment: an Assigned To column that resolves to real, notifiable accounts
  • Approvals and reviews: Approver and Reviewer columns scoped to the right people
  • Document ownership: every policy and procedure carries an accountable owner
  • Contact directories: department lists where each entry links to a live profile
  • Request routing: submitter and handler fields that automations can act on
  • Team rosters: project lists capturing multiple members in one multi-select column

Benefits

  • Validated identities: the picker resolves against the organization directory, so names are never misspelled or stale
  • Profile integration: entries connect to the person’s photo, contact details, and profile card
  • [Me] filtering: one view filtered to [Me] shows every visitor their own items
  • Automation ready: flows reading the column get a resolvable account with an email address
  • Flexible scope: allow one person or many, people only or people and groups
  • Consistent with SharePoint itself: Created By and Modified By use the same column type

How It Works

  • People picker entry: type-ahead suggestions match names against the directory as users type
  • Accounts, not strings: the column stores a reference to the user, staying current if display names change
  • Group scoping: the picker can be limited to members of one SharePoint group instead of the whole directory
  • People or groups: a setting controls whether SharePoint groups can be selected alongside individuals
  • Display options: views can show the name, picture, email, or another profile field for each stored person

Limits and Nuances

  • Directory dependent: only accounts known to the tenant resolve; external people must exist as guests first
  • Multi-value indexing: columns allowing multiple selections cannot be indexed, which matters on very large lists
  • No formula access: calculated column formulas cannot reference Person or Group columns
  • Group values: when groups are allowed, an item may store a group rather than a person, which workflows expecting one individual must handle
  • Departed users: names of people removed from the directory can linger on historical items
  • Scoping is per column: the SharePoint group used for scoping is set on each column, so plan group membership maintenance

Common Questions About the Person or Group Column

What is a Person or Group column in SharePoint?

It is a column type that stores validated user accounts rather than typed names. Users select people through a type-ahead picker that resolves entries against the organization directory, so every value is a real account with a profile and an email address. SharePoint uses the same column type internally for the built-in Created By and Modified By columns.

Can I limit who appears in the people picker?

Yes. The choose-from setting scopes the picker either to all users or to the members of one specific SharePoint group. Scoping to a group is the standard way to keep an Approver column limited to actual approvers rather than the entire directory. A related setting controls whether the column accepts people only or people and groups.

Can a Person column hold more than one person?

Yes. Enabling multiple selections lets a single field store several people or groups, which suits scenarios like project team members or multiple reviewers. The tradeoff is that multi-value person columns cannot be indexed, which matters for filtering very large lists, and automations need to handle the value as a collection rather than a single account.

Why can’t I find someone in the people picker?

The picker only resolves accounts the directory knows about. People outside the organization will not appear unless they already exist as guests in the tenant, and brand-new accounts can take a short time to become visible. If the column is scoped to a specific SharePoint group, anyone outside that group will not appear either, by design.

How do Person columns improve views and automation?

Because values are real accounts, a view can filter on [Me] to show each visitor only their own items, so one list serves every user personally. Display options let views show the name, picture, or other profile details. Automation benefits too: a flow reading a Person column gets a resolvable identity with an email address, not a string to guess at.

Should I use a Person column instead of a text column for names?

Almost always. Typed names go stale, get misspelled, and cannot drive notifications. Greg Zelfond builds LookBook 365 trackers with Person or Group columns for every owner, approver, and assignee field, because validated identities enable [Me] views, profile cards, and reliable automation while remaining completely out of the box with no custom development.