Put someone’s name in the Authors or Contributors field on a page and they can edit that page. There is nothing else to configure, no override to create and no role to change: the byline is the grant. It is the cheapest way to let a Restricted freelancer work on the one article they were hired to write, and the reason a Read Only teammate can still fix a typo in something they helped produce.
Where you set it
Open the page, then in the editor’s right rail choose the Page settings tab and expand Page Details. Authors and Contributors are two searchable multi-selects listing the members of your workspace. Both save as you change them, like everything else in the editor.
Editing them needs only the rights you already need to edit the page, so anyone who can work on a page can add a collaborator to it. The two fields sit alongside the rest of the page’s metadata described in Page Settings.
A person is one or the other
The two lists are mutually exclusive. Add somebody as an author and they are removed from contributors in the same edit; add them as a contributor and they leave the authors list. You never have to clean up the other field, and a name will never appear twice on one page.
For access it makes no difference which list someone is in — both grant exactly the same thing. The distinction is editorial, and it is the one your site templates read when they render a byline.
What the grant actually is
Whenever Leed looks up a member’s access overrides, it also assembles a synthetic page override at Content Writer level for every page where that member appears as an author or a contributor. It behaves precisely like a per-page Contributor override that you never had to create, and it sits alongside any explicit access the member already holds — the strongest one wins.
Because it is an ordinary page-level grant, it is one of the four things that can satisfy a check on a page, alongside an override on the page, its page type or one of its labels. Resource-Level Access Overrides has the diagram.
How far it reaches
| Action | Author or contributor on the page | Why |
|---|---|---|
| See the page in their page list | Yes | A Content Writer grant clears the Read-level check the list applies |
| Open and edit the page | Yes | Editing a page needs Content Writer, which is exactly what the byline grants |
| Publish or schedule it | No | Publishing needs Content Publisher; a Writer-level grant cannot reach it |
| Delete it | No | Deleting is gated at the same level as publishing |
| Create a new page | No | Creating is not an action on any existing page, so no page grant applies |
| Edit other pages of the same type | No | The grant names one page and nothing else |
| Edit other pages carrying the same label | No | Same — a byline is never a scope |
Creating and publishing stay with Content Publisher no matter how many bylines somebody carries; the ladder is in Roles and Permissions. In practice that means a byline-only collaborator needs a Content Publisher to create the page first and to publish it afterwards.
It follows the latest revision
The grant is computed from the author and contributor lists on the page’s latest revision, for CMS-managed pages that have not been deleted, in the workspace you are signed in to.
The practical consequence is that access is self-cleaning. Take somebody off the lists, and as soon as that edit becomes the latest revision their access to the page is gone — there is no override to hunt down and delete, and no audit to run later. It also means the lists on an older revision are irrelevant to access: what is on the current one is what counts.
Why this matters
A Restricted writer can work on exactly their own pages. Give an outside writer the Restricted role, which hides essentially everything, then name them as the author of the three articles they are producing. Those three pages appear in their tree and open in the editor; nothing else does.
A Read Only member can fix the content they helped write. Read Only sees the workspace but changes nothing. Listed as a contributor on a page, the same person can go in and correct it, without a role change that would also let them edit every other page in the workspace.
Finding pages by byline
The page list carries an Author column and a Contributors column, and each column header has a filter that narrows the list to the members you pick. It is the fast way to answer “what is this person on the hook for?” before a holiday or a hand-over.
Both are CMS-only filters: they change what you see in the workspace, not what your site publishes. Those columns and the rest of the page list are covered in Managing Pages.
Bylines on your published site
The same two fields do a second, entirely separate job: they are what your templates render as a byline. That half has its own condition, and it is not on the page — it is on the member.
A member reaches your published site only when Available to Templates is ticked on their row and they have a Slug. The slug is not optional decoration: when Leed writes the member list out for the site build, anyone without a slug is written as not visible regardless of the checkbox, so ticking the box alone silently does nothing. Both settings are on the member’s expanded row in Managing Team Members.
Once a member is published, templates render them from the site’s member list — by page, through the authors helper, or by looking up an individual member. The helpers that do it are in Collection, Lookup and Series Helpers.
So a person can be an author for access purposes and invisible on the site, or visible on the site and named on no pages at all. The two jobs share a field and nothing else.
Byline or override?
If you find yourself adding the same person to every page of a type as it is created, stop and grant them a Contributor override on that page type instead; it covers the pages that do not exist yet, which a byline never can. Conversely, do not reach for an override to solve a single article: the byline is free on every plan, needs no administrator, and disappears on its own when the name comes off.
Neither of them defeats a private page — a page marked private stays visible only to whoever created it, byline or no byline. See Private Pages.