Authorization for your industry.
Every industry has its own rules about who may do what. The question under them is the same: may this person, service, or agent take this action on this record, right now? Here is how ZStrike applies in six industries.
Give every tenant its own roles. Keep one policy set.
Every service in a multi-product SaaS answers the same question its own way: may this user, in this tenant, do this to that record? ZStrike answers it from one policy set, beside each service.
Tenant isolation
A user reaches only the records of their own tenant, in every product. The rule is written once, not repeated in every query.
Policytenant-isolation Roles each customer controls
Your customer's admin assigns roles. Policies read the role and the attributes of the record, so a new role does not need a code change.
Policytenant-role-access Changes that do not break other teams
Many teams edit one policy set. Impact analysis shows which recent decisions a draft would flip before anyone merges it.
Featureimpact analysis Put limits on money movement. For people and for agents.
Payments, refunds, and transfers carry rules about amount, role, and separation of duties. ZStrike checks each action against those rules before it reaches your ledger.
Dual control on transfers
A transfer above a threshold needs a second approver, and the person who started it cannot approve it.
Policydual-control-wire Hard caps for AI agents
An agent refunds up to a cap. The cap is a policy, so no prompt can raise it, and every attempt above it is on the record.
Policyagent-refund-cap An answer for every review
Each decision records the rule and the policy version behind it. A question about an approval from last quarter is one query.
Featureaudit trail Open a chart for the care team only. Explain every access.
Access to a patient record depends on the relationship between the person and the patient, not on a job title. ZStrike decides from that relationship and logs the reason each time.
Care-team-only access
A clinician opens a chart only while they are on that patient's care team. Everyone else is denied, with the rule named.
Policycare-team-only Emergency access with a reason
Emergency access is its own rule. It requires a stated reason in the request, and every use lands in the audit trail.
Policyemergency-access Agents that read patient data
Decisions are session-aware. An agent that has read patient records can be denied export calls for the rest of that session.
Policyno-export-after-chart-read Wall off every matter. Show that the wall held.
A firm's documents belong to matters, and matters have conflicts. ZStrike turns the matter team and the conflict list into rules that every document request passes through.
Matter-based access
Only the people assigned to a matter open its documents. Assignment changes take effect on the next request.
Policymatter-team-only Ethical walls
A forbid rule blocks anyone on a conflicting matter, whatever role they hold. A forbid always overrides a permit.
Policyethical-wall Proof for the client
When a client asks who could see their files, the audit trail answers with the rule and the version behind each decision.
Featureaudit trail Cap what support can give away. Bots included.
Refunds, credits, and seller tools are where retail permissions go wrong. ZStrike applies the same limits to a support agent, a support bot, and a seller's staff.
Refund and credit limits
Support staff and support bots refund up to a limit set by role. Above it, the check denies and names the rule, so your app can route the request.
Policysupport-refund-limit Seller scopes on a marketplace
A seller's staff manage that seller's listings and orders only. One rule covers every seller.
Policyseller-scope Payment details behind their own permission
Staff see an order's history. Field-level rules keep payment details behind a separate permission.
Policypayment-fields Match authority to the claim. Not to the job title.
Who may approve a claim depends on its size, its state, and who is involved. ZStrike evaluates those attributes on every action instead of a fixed role list.
Claims authority limits
An adjuster approves claims up to their authority limit. A larger claim needs an approver with a higher limit.
Policyclaims-authority Licensed-state rules
An adjuster or agent works only on policies in the states where they hold a license.
Policylicensed-state No self-dealing
A forbid rule blocks anyone from handling a claim where they are the claimant or the payee.
Policyno-self-dealing Your industry is not here? The check is the same.
Bring one real permission check. We model it in Cedar, live.