Last updated: June 2026
Creating your workspace. When you first sign up, you will create a workspace for your company. Enter your company name, jurisdiction, and entity type. This is the container for all your governance data.
Connecting your AI. sanctor uses Anthropic's Claude to classify your provisions. You will need a Claude API key. Enter it in Settings under Workspace. If you do not have a key yet, you can sign up at anthropic.com and create one. You can skip this step during onboarding and add the key later.
Your first provision. Go to Governance, then Provisions. Write a provision in the text area. This can be any clause from your bylaws, operating agreement, policy or other authoritative document. Click "Map this" and the AI will classify it, identifying roles, actions, conditions, thresholds, and terms. Review the classification and confirm.
Adding people. Go to Governance, then People & Roles. Add the people in your company: directors, shareholders, officers, anyone referenced in your governance documents. Assign each person to the groups that the provisions define.
Uploading existing documents. If you already have documents, you can upload the document instead of writing provisions one at a time. Go to Governance, then Provisions, and click "Upload a document." The AI will split the document into individual provisions and classify each one. You review and confirm.
Operative provisions create rights, powers, obligations, or restrictions. They become nodes in the governance graph. Example: "The Board of Directors may approve capital expenditures up to $50,000."
Definition provisions define a term. They are saved to the glossary and applied globally. Example: "'Board of Directors' means the directors of the Company appointed in accordance with these Bylaws."
Interpretation provisions modify a term's meaning within a specific scope. They are applied only where relevant. Example: "For the purposes of share issuance, 'Shareholders' means only those holding voting shares at the record date."
Context provisions are background or recitals. They are saved as document notes and provide context but do not create authority. Example: "The Company is incorporated under the laws of the State of Wyoming."
The authority engine answers one question: can this person take this action?
It works in five steps:
Documents organise your provisions into formal governance instruments. A workspace can have multiple documents: bylaws, operating agreements, policies, contracts. All documents share the same governance graph and the same people registry.
To create a document, go to Governance and start adding provisions. Select which document each provision belongs to. Once complete, the system can assemble the document in formal order: title, parties, recitals, definitions, operative provisions, execution block.
Extensions are optional functional layers that bind to your provisions and derive their behaviour from them.
Cap table. Live shareholdings, voting percentages, vesting schedules, and threshold alerts derived from share-related provisions.
Resolutions. Create, vote on, and track resolutions. Reads thresholds from provisions. Tracks votes in real time. Generates formal minutes automatically.
Compliance. A calendar of deadlines and obligations generated from every temporal provision in your workspace. Reminders, deadline tracking, and overdue alerts.
Payments. Distributes payments via Stripe Connect according to the formula in a bound provision. When the provision is amended, the next payment reflects the change.
Registers. Share register, director register, and member register. Each entry is backed by an authorised governance action.
Signing. Digital signatures for assembled governance documents with a tamper-evident record.
Audit trail. An immutable log of every governance action taken in the workspace. Every authority check, vote, share movement, payment, amendment, and signature.
AI governance agent. Monitors legal and regulatory changes relevant to your jurisdiction. Proposes amendments when external rules change. Proposals enter the standard governance workflow.
Digital treasury. Manages digital assets through the governance framework. A regulated wallet provider operates behind the scenes. Provisions govern allocations, yield, and withdrawals.
When the authority engine determines that an action requires approval, the user can create a proposal. The proposal identifies the action, the governing provision, the required threshold, and the eligible voters.
Eligible voters are notified by email, SMS, or in-app notification. They can approve, discuss, or reject with a counter-proposal. Counter-proposals are structured alternatives, not comments.
When the vote reaches the required threshold, a resolution is recorded. If the proposal was to amend a provision, the amendment is applied automatically and the governance graph updates.
Governing documents change through their own rules. A user proposes a change. The engine checks whether the change is authorised under the document's amendment provisions. If a resolution passes, the provision is updated, the AI reclassifies it, and the graph reflects the new rules. Every amendment creates a new version. Previous versions are preserved.
Contact support@sanctor.io. We respond within 24 hours on business days.
The following are emails you will receive from our systems. If anything looks different please report it to us as it could be a spam email.