Staff users should document which roles have access to the analytics
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start in the /staff documentation, especially the Roles & Permissions section. Clarify which roles can access analytics, and consider the work done when that access information is documented alongside the existing write and publish permissions.
Written by the indexing model from the issue text.
Description
Path: /staff
Currently, the Roles & Permissions docs describe who can write and publish, but are silent on who can access analytics. It would be helpful to clarify that.
- Dominant language
- MDX
- Stars
- 13
- Forks
- 32
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TryGhost/Docs
-
Dependency Dashboard Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·