Every user sees and does only their part.
Designing business software permissions: roles, branches, separating creation from approval, and an activity log, to protect data and reduce errors.
Permissions are a management decision, not a technical detail: who creates an invoice, who approves it, who sees the numbers. We define them with you in a clear matrix before building.
- Clear roles
- Branch scopes
- Separate approval
- Activity log
Principles we follow
- The least access needed to do the job.
- Whoever creates a key operation does not approve it.
- Access scoped to branch or department.
- A log of every important edit or deletion.
Some of our clients
- iHouse — Brand, website and connected product development.
- MAQR — A platform for workspace discovery and booking.
- Dareebty — A digital product for electronic invoicing workflows.
- Aviation Sporting Club — Development and maintenance of the club's systems.
- Roaya Aluminum — Business, inventory and manufacturing systems.
- Sycamore Furniture — Manufacturing management at the core of the system.
- Bin Noah Furniture — One ERP system for the furniture business.
- BANKA Furniture — From the website to business systems and infrastructure.
Frequently asked questions
How do we separate creating from approving?
With two roles: one creates and submits, the other approves or rejects with a reason; nothing executes before approval.
What do you need to scope the work?
How you work today, the systems and files you use, who will use the system and the main daily problems. Send them in the brief and we start there.
- Start with approvals and employee files.
- Every item in its place, in every branch.
- Your customer tracks their own request.
- Start your project brief
- Web Weavers — Websites & digital experiences
- Support Squad — IT solutions
- Swift Dev — Software & custom solutions
- ECCO Connect — Contact centers & customer service
- Creative Sparks — Marketing, identity & content
- Power Pros — Electrical & smart space solutions
- Back Office — ECCO Connect