Security and control
Control where access starts. Know where actions leave a record.
Your account, your workspace, your role and the project relationship you are connected on decide what you can reach. Sharing between a customer and a provider is a deliberate decision, not a default. Project money and automated actions leave records that are added to, not rewritten.
This page describes controls built into the product, not certifications. For legal disclosure, see the Privacy Notice.
The access model
Access is layered. A role on its own does not unlock everything.
Your plan determines what is available. Your role determines what you can do. Project scope determines which records you can work with.
- Account
- Personal and Pro are separate account types.
- Workspace
- Pro work happens inside a workspace you belong to.
- Role
- Your role decides which actions you can take.
- Relationship
- A project connection decides what can cross to a customer.
- Project scope
- Some roles only reach the projects assigned to them.
01 · Who can see what
Access is scoped before a screen is drawn.
Personal accounts and Pro workspaces are separate. Working in a Pro workspace requires membership in it and eligible Pro access. Inside, every member has a real role, and that role is checked on the server when the action runs, not only in the interface.
- Roles mean something
- Sales and Marketing reach only their own or assigned projects. Compliance is read and audit only. Support has no project or payment scope.
- Some actions stay with the owner
- Deleting a workspace and transferring ownership stay with the owner.
A role never widens what a plan includes, and it never reaches past project scope.
03 · Every project dollar has a record
Every project dollar has a record.
Project money is held as one record per transaction, counted in whole cents, with status derived from the transaction itself rather than typed in by hand. Those amounts post to a project funds ledger that only accepts new entries.
- Entries are not edited or deleted. A refund, dispute or reversal is written as a further record.
- Differences are surfaced. Reconciliation reports a discrepancy for review instead of adjusting the ledger to match.
- Disbursements are reviewed. Approval and the transfer itself are separate, explicit actions.
Card and payout infrastructure is handled by Stripe. Provider payouts are available for Canadian businesses in CAD today.
04 · AI with boundaries
Nothing starts running because ClickSabi suggested it.
A provider builds an automation and turns it on. Each run is recorded with the reason it fired and the automation it came from, so an automated message can be traced back.
Where AI reads your information, it works from what you gave it, and a recommendation is built to show the context behind it. AI output informs a decision. It does not make one for you.
Plain limits
Clear about the boundaries.
Where something sits with a supplier or is not available yet, we say so rather than dress it up.
- Payment cards
- Card and payout banking details are collected and handled by Stripe on their own pages. ClickSabi does not store them.
- Provider payouts
- Provider payouts today cover Canadian businesses in CAD. Requests outside that are not processed.
- Certifications
- ClickSabi holds no security certification of its own today, and we do not present a supplier's as ours.
- Infrastructure
- Hosting, storage and network protections sit with our infrastructure providers, so we describe the product controls we can point to instead.
- Reporting an issue
- Found a problem or suspect unauthorised access? Contact us with enough detail to reproduce it, and do not access other people's data while testing. We do not run a paid bounty programme.
FAQ