Owner
An Owner is the Salesforce user (or queue) recorded in a record's OwnerId field as the person responsible for that record.
Definition
An Owner is the Salesforce user (or queue) recorded in a record's OwnerId field as the person responsible for that record. The owner has full read and edit access to the record by default, and that ownership decides where the record sits in the role hierarchy for sharing and reporting.
Ownership is one of the load-bearing parts of the Salesforce sharing model. When someone creates a record, they become the owner, and Salesforce writes a sharing row that grants the owner access. Other users then reach the record through the role hierarchy, sharing rules, manual sharing, or teams. Almost every record has an owner, the main exception being detail records in a master-detail relationship, which inherit access from their parent.
How ownership drives access, sharing, and reporting
The OwnerId field and who can hold it
Every standard and custom object that supports ownership has an OwnerId field. It points to either a user or, for objects that allow it, a queue. When a user saves a new record, Salesforce stamps their ID into OwnerId and treats them as fully responsible for that record. Detail records in a master-detail relationship are the notable exception. They have no owner of their own and take their access from the master record instead. That is why you cannot set sharing or an owner directly on a detail record. Ownership is not the same as a permission. A profile or permission set decides whether a user can touch a given object at all. Ownership decides who is accountable for a specific row and seeds the baseline access for it. A user can own a record on an object even while organization-wide defaults keep everyone else out. This split between object-level permissions and row-level ownership is what lets one Account stay visible to its owner and their managers while staying private from the rest of the company.
Sharing rows are created the moment a record is owned
Behind the scenes, Salesforce keeps a share table for each object. When a record gets an owner, the platform adds a row to that share table granting the owner access, with a reason code that records why the access exists. The Salesforce engineering team describes this in their post on record ownership: the owner field, the object share tables, and the group membership tables work together to decide who sees what. The role hierarchy rides on top of this. Users higher in the hierarchy inherit the same access as the people who report to them, so a manager can see, edit, and report on records owned by their team without anyone sharing those records by hand. Salesforce maintains role groups internally to make that inheritance work without a separate share row for every manager. The practical takeaway is that changing an owner does more than relabel a field. It rewrites who inherits access up the chain, which is why ownership and the role hierarchy are always discussed together.
Owner-based sharing rules
Owner-based sharing rules use ownership directly to widen access. You pick a set of users by role, public group, or queue, then say who their records should be shared with and at what access level. A common example from the Salesforce documentation: sales reps in the same role should see each other's accounts even though the org-wide default for Account is Private. An owner-based rule covers exactly that case. This is different from a criteria-based sharing rule, which keys off field values rather than who owns the record. Owner-based rules answer the question who owns it, while criteria-based rules answer what is in it. Records can be shared out to roles, roles and subordinates, public groups, territories, and portal roles, with access levels from Read Only up to Read/Write. Because the rule is tied to ownership, transferring a record to a new owner can move it in or out of a sharing rule's reach automatically. Plan ownership and sharing rules together, or access can shift in ways you did not intend.
Changing a record owner and what travels with it
You change an owner from the record itself using the Change link next to the owner's name. You can send a notification email to the new owner, and depending on the object you can choose which related items move too. For an Account, the contacts owned by the old owner, that owner's open opportunities, draft and in-approval contracts, and draft orders transfer automatically. Open activities also move, while closed activities stay put. Other items are optional and need a checkbox: open opportunities owned by other users, the account owner's closed opportunities, and open or all cases. The new owner must already have at least Read access to a parent account, or the person doing the transfer must be able to share that account, otherwise the change fails. One gotcha worth memorizing: a workflow rule or Flow that updates the owner field does not transfer the related items the way the Change button does. If you reassign owners through automation, related records can be stranded under the previous owner unless you handle them yourself.
Permissions needed to reassign ownership
Not everyone can change an owner. To transfer a single record, a user generally needs the Transfer Record permission, granted through a profile or a permission set, plus edit access to the record in question. If the user neither owns the record nor has it shared to them through the role hierarchy or sharing rules, they typically need Modify All Data or the relevant transfer permission to reassign it. This is the source of the common Insufficient Privileges error when someone tries and fails to change an account owner. The fix is almost always a missing Transfer Record permission, restricted object access, or a validation rule or Apex trigger blocking the save. Because mass reassignment is powerful, treat the Transfer Record permission as sensitive. Hand it out through permission sets to the specific admins and team leads who manage territory moves, rather than baking it into a broad profile that many users share.
Queues as owners and ownership in practice
Some objects, including Leads, Cases, and custom objects you enable for queues, let a queue hold ownership instead of a person. A queue-owned record is parked and waiting. Anyone who is a member of the queue can pick it up and take ownership, which is how round-robin and shared work pools are built. The OwnerId still points to an owner, it just resolves to a queue rather than a single user. Reports and list views can filter on that to show unassigned work. In a mature org, ownership is treated as data that has to stay correct. Records need real owners, ownership transfers when reps change territories or leave, and ownership-based reports such as My Open Cases or My Team's Pipeline drive accountability. When ownership drifts, reports go wrong and the sharing model quietly leaks or over-restricts access. Keeping OwnerId accurate is one of the cheapest ways to keep both security and reporting honest.
How to change a record's owner
Changing a record's owner reassigns responsibility and rewrites the access that flows from ownership. Here is the standard manual flow on a single record, plus the choices you make along the way.
- Open the record and start the change
Go to the record detail page. Find the Owner field and click the Change link next to the current owner's name. You need edit access to the record and the Transfer Record permission to see this option.
- Pick the new owner
Select a user, or a queue on objects that support queue ownership. Confirm the new owner already has at least Read access to any parent record, such as the Account behind a Case or Opportunity, or the transfer will fail.
- Choose related items and notification
Optionally select which related records move with the owner, such as open opportunities owned by others or open and closed cases. Tick Send Notification Email if you want Salesforce to alert the new owner.
- Save and verify access
Save the change. Spot-check that the new owner and their managers in the role hierarchy can see the record, and that any owner-based sharing rule still grants the access you expect after the move.
The system permission that lets a user reassign records they can edit; grant it through a permission set to the admins and leads who manage ownership.
An optional checkbox that emails the new owner when ownership changes, so the handoff is visible rather than silent.
Per-object checkboxes that decide which open or closed related records move with the owner; closed activities never transfer.
- A workflow rule or Flow that sets the owner field does not transfer related items the way the Change button does; reassign related records yourself when you automate ownership.
- An Insufficient Privileges error on transfer usually means a missing Transfer Record permission, restricted object access, or a validation rule or trigger blocking the save.
- Detail records in a master-detail relationship have no owner; you cannot reassign them directly because they inherit access from the master record.
Prefer this walkthrough as its own page? How to Owner in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Change a Record's OwnerSalesforce
- Considerations for Changing a Record's OwnerSalesforce
- Behind the Scenes of Record Ownership in SalesforceSalesforce
Straight from the source - Salesforce's reference material on Owner.
- Change a Record's OwnerSalesforce
- Create Owner-Based Sharing RulesSalesforce
Hands-on resources to go deeper on Owner.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What level of access does the Owner of a Salesforce record have to that record by default?
Q2. How does a record's Owner influence the role hierarchy for sharing and reporting?
Q3. When a rep is promoted and her accounts are redistributed, which field does the Mass Transfer tool update so each record's Owner changes?
Discussion
Loading discussion…