App permissions: add branch-scope UI copy fixture
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- electron, javascript
Research direction
No file or test path is named. Start by locating the permission screen and its existing copy fixtures, then add synthetic entries for one, selected, and all branches across inventory, sales, and customer scopes. Done means the fixture includes readable non-technical wording and a clearly marked negative example without real secrets or records.
Written by the indexing model from the issue text.
Description
Parent: #34
Problem
The permission screen needs short readable text that explains branch access without using internal ACL language.
Boundary
Copy fixture only. Do not redesign the whole permission screen.
Acceptance criteria
- Add a fixture/table of permission text for one branch, selected branches, and all branches.
- Include examples for inventory, sales, and customer scopes.
- Keep wording understandable for non-technical shop owners.
- Include at least one negative example that should not be used because it hides data access.
Safety notes
Use synthetic examples only. Do not include live credentials, production customer records, private webhook payloads, payment details, or real API keys in public issues, fixtures, logs, screenshots, or PRs.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 516
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 Posnic/POS
-
area: localization bug good first issue help wanted size: small
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-2 days Newbie friendliness 72/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-2 days Newbie friendliness 76/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·