Manage staff, personas, and tags
Keep access, bylines, desk voices, and coverage navigation accurate as the newsroom changes.
- People access
- Settings → Staff
- Desk voices
- Admin → Personas
- Coverage labels
- Admin → Tags
Maintain the staff roster
Settings → Staff grants News Desk roles to existing website usernames. The role determines access; the display name is the friendly desk label. Payroll manager is a separate editor permission.
- Use the exact main-account username.
- Choose Contributor or Staff Author for most writers and production helpers.
- Reserve Editor for people who can publish and manage coverage feeds.
- Reserve Admin for people who manage credentials, staff, content types, and desk-wide settings.
- Deactivate people who leave; review their open assignments before removing the main account.
Manage personas
A persona is a branded WNY Athletics desk voice used for bylines and AI-assisted recap rotation. It is not a login and never produces a payable.
-
Use a clear desk name
Choose a name readers can recognize as a coverage desk voice. The slug becomes a stable identifier; avoid changing it after integrations or exports use it.
-
Add honest voice notes
Describe tone, pacing, vocabulary, and coverage focus. Do not invent a biography or human credentials.
-
Upload an approved avatar
Use JPG, PNG, or WebP within the displayed size limit. The public persona page may show it.
-
Set sport affinities and rotation weight
Sport affinities guide recap assignment. Weight controls relative rotation; zero keeps the persona available for manual assignment but out of automatic rotation.
-
Retire instead of delete
A referenced persona cannot be deleted. Retiring preserves historical bylines and removes it from active use.
Manage tags and groups
Tags connect posts to sports, teams, sections, content collections, filters, and the public coverage rail. Groups organize that catalog so writers can find the right labels.
-
Search before creating
Check common abbreviations, school variants, and existing groups. Duplicate tags split public archives.
-
Use a stable slug
Slugs power URLs and integrations. Archive a tag rather than reusing its slug for a different subject.
-
Choose listing placement
Content type and subcategory chips affect how a tag appears in public listing filters.
-
Pin only useful coverage-rail items
The header rail is scarce space. Pin the sports or collections readers need now, then order them deliberately.
-
Build groups for staff usability
Sport dropdown groups and parent/child groups keep a large tag catalog navigable without changing the public meaning of a tag.
Monthly maintenance
- Deactivate staff who no longer work the desk and reassign open posts.
- Review editor and admin roles for least-privilege access.
- Retire unused personas and confirm active voice notes still match the brand.
- Review persona rotation so one desk voice is not overused.
- Archive duplicate or obsolete tags without changing slugs on live archives.
- Update the public coverage rail for the current sports season.
Frequently asked questions
Can I delete a persona that has published stories?
No. Retire it so historical references remain intact.
Does a persona need a website login?
No. It is a desk voice/byline, not a person account.
Why can’t I reuse an archived tag slug?
The slug remains reserved so old URLs and records cannot silently change meaning.
Who should be a News Desk admin?
Only people who need staff, credential, content-type, taxonomy, and desk-wide settings access.