Product, Room, Dispute and Elite Settings
The four smallest tabs in Features Configuration — three of them are pure permissions, and one is GPS attendance.
Four tabs are short enough to cover together.
Product Settings
Nothing but the Product permission category, split by role. This is where you decide who may create products, edit their prices and stock, and sell them.
Worth a thought if you carry retail: a stylist who can sell a product but not edit it is usually the right shape. Editing stock levels is how inventory counts drift.
Room Settings
Nothing but the Room permission category. Who may create and manage rooms, and assign them to services.
Dispute Settings
Nothing but the Dispute permission category. Who may view a payment dispute and respond to it.
Keep this narrow. A dispute response is a legal document to the card network, and there is one chance to submit it. See Handle a payment dispute.
Elite Features
Only visible on Elite plans.
Mark Absent With GPS — when a stylist is far from the shop, mark them absent and block them from creating tickets.
Absence distance in meters — how far counts as far.
This is a strong tool and a blunt one. It will misfire in a building with poor GPS, and it stops someone working rather than just flagging it. Set the distance generously — a whole block, not a doorway — and tell your team it is on before you switch it.
Integrations
Two actions rather than settings:
Create Token — issues an API token for another system to call Perceny as your business. Tokens carry scopes; give each integration only the scopes it needs, and revoke rather than reuse when a vendor changes.
Add Webhook — Perceny calls a URL you own when something happens, so another system can react without polling.
Both are covered in Connect Perceny to another system.