# Your Company Help Center This is a purpose-built SaturnDocs demonstration. Your Company and its contract platform are fictional; no customer content or customer claim appears here. ## Explore Your Company [Getting Started](/getting-started/workspace-setup) Set up your Workspace, invite your team, and bring existing contracts into Your Company. [Working with Contracts](/contracts/create-from-template) Create a Matter, negotiate each Turn, route approvals, and prepare an Executed Copy. [For Counterparties](/counterparties/reviewing-a-contract-sent-to-you) Review a document and propose changes through a secure, account-free link. Your Company is currently on version 4.2. See [what changed](/release-notes/v4-2) or [contact support](/support/contact-support) for help from a person. # Set up your Workspace A Workspace contains your team, Matters, Templates, Clause Library, Playbooks, and approval rules. An Admin should complete the initial setup before the team starts drafting contracts. Add your organization details Open **Settings > Workspace profile**. Enter the legal entity name, business address, default governing law, and primary contract contact. Your Company can insert these values into Template variables. Choose Matter conventions Under **Matter settings**, choose a default owner, date format, currency, and identifier format. A clear identifier such as `RL-2026-0042` makes Matters easier to reconcile with your CRM or finance system. Configure review defaults Set the standard counterparty review period and decide whether review links expire automatically. You can override both settings for an individual Matter. Set renewal rules Choose the default Renewal Reminder schedule. Many teams use reminders 120, 90, and 30 days before the notice deadline, not the renewal date. Use the notice deadline as the primary renewal trigger. It is usually the last practical date to prevent an unwanted automatic renewal. Next, [invite your team](/getting-started/inviting-your-team) and assign each member the least-permissive role that supports their work. # Invite your team Workspace members have paid seats and sign in to Your Company. External counterparties do not need a seat when they use a secure review link. ## Choose a role Admin Manages Workspace settings, members, Templates, the Clause Library, Playbooks, and all Matters. Editor Creates and edits Matters, drafts documents, manages Turns, and sends counterparty reviews. Approver Reviews approval requests and records decisions. Access is limited to Matters routed to them unless separately granted. Viewer Reads permitted Matters and downloads documents but cannot change contract content or workflow state. ## Send invitations Open the members page Go to **Settings > Members**, then select **Invite members**. Add people and roles Enter one or more work email addresses. Assign a role to each person. You can change roles later without removing Matter history. Review access Select **Send invitations**. Invitations expire after seven days. An Admin can resend or revoke a pending invitation from the members page. Approval Chain membership does not automatically grant broad Workspace access. An Approver can open the specific Matter and documents needed for the decision. If your organization uses single sign-on, review [sign-in and SSO troubleshooting](/troubleshooting/sign-in-and-sso) before inviting the full team. # Import legacy contracts Import signed agreements as historical Matters to create a complete contract record. A legacy import does not recreate negotiation Turns. It stores the final document as the Executed Copy and captures the dates and obligations your team still needs to manage. ## Prepare your files Use searchable PDF or DOCX files up to 50 MB. Remove password protection before upload and use one file per primary agreement. Add amendments and schedules as separate documents within the same Matter. Create an import Open **Matters**, select **Import contracts**, and upload up to 100 files. Your Company creates a draft import row for each primary agreement. Confirm extracted fields Review the counterparty, agreement type, effective date, term, renewal behavior, notice deadline, and governing law. Low-confidence values are highlighted for manual review. Attach related documents Add amendments, exhibits, and schedules to the matching Matter. Label each file so the document timeline remains clear. Publish the records Assign an owner and select **Complete import**. Your Company marks the primary file as the Executed Copy and schedules Renewal Reminders from the confirmed dates. Your Company can suggest extracted values, but your team is responsible for verifying deadlines and obligations against the signed agreement. For rejected or unreadable files, see [document upload errors](/troubleshooting/document-upload-errors). # Create a contract from a Template A Template combines approved contract language with variables such as party name, fees, term, and governing law. Creating from a Template keeps the first draft consistent and gives reviewers a clear starting point. Start a Matter Select **New Matter** from the Workspace header. Choose the agreement type, name the counterparty, assign an internal owner, and select a target signature date. Choose a Template Your Company shows Templates available for the agreement type and legal entity. Check the Template version and owner before continuing. Complete the variables Enter each required value. Your Company previews every location where a value will appear and flags inconsistent dates, currencies, or party names. Review suggested clauses If a Playbook is attached, review any alternative language suggested for the deal profile. Add approved clauses from the Clause Library when the contract needs terms not included in the base Template. Create the first draft Select **Create draft**. Your Company saves version 1 in the Matter and records the Template version and variable values in the activity history. Keep deal-specific facts in variables rather than editing repeated text. This reduces mismatches between the commercial summary and the contract body. When the draft is ready, [send it for counterparty review](/counterparties/reviewing-a-contract-sent-to-you) or learn the [redlining basics](/contracts/redlining-basics). # Redlining basics A **Turn** is one complete round of proposed changes from one side of a negotiation. Your Company keeps every Turn in order, so the Matter shows who changed the document, when they returned it, and which version became the next working draft. ## Review a Turn Open the latest document and select **Review changes**. Additions appear with an underline, deletions appear struck through, and comments remain attached to the relevant text. Work clause by clause Use the change list to move through each proposal. Your Company groups nearby edits so a rewritten sentence is reviewed as one decision. Accept or reject changes Select **Accept** to incorporate a proposal or **Reject** to keep the prior language. You can apply a decision to one change, a selected group, or all remaining formatting-only changes. Use the Playbook Version 4.2 shows the preferred position, approved fallback language, and escalation guidance beside supported clauses. Insert a fallback without leaving the review. Complete your Turn Resolve required comments, review the clean preview, and select **Complete Turn**. Your Company locks the returned version and creates the next working draft. Completing a Turn cannot be undone. You can start another Turn, but the completed version remains in the Matter history. If a proposed term exceeds the Playbook boundary, route the Matter through an [Approval Chain](/contracts/approval-chains). # Approval Chains An Approval Chain is an ordered set of internal decisions required before a Matter can move forward. Chains can be selected manually or triggered by facts such as contract value, agreement type, nonstandard liability, or a Playbook exception. ## How routing works Each stage can contain one approver or an approval group. Stages run in order. Within a group, the Workspace Admin can require one decision or unanimous approval. Your Company records the request, supporting note, decision, and timestamp in the Matter. Request approval From the Matter, select **Request approval**. Your Company recommends a chain from the agreement type and current terms. Confirm the chain and summarize the decision needed. Attach the right version Choose the document version the approvers should review. The request remains linked to that version even if negotiation continues. Track each stage The Matter status shows the current approver and due date. Reminders are sent automatically. Editors can add context without restarting the chain. Respond to the decision An approval advances the request. A rejection returns it to the Matter owner with the approver's required changes. Submit a new request after revising the contract. In version 4.1, approvers can delegate a stage for a defined period. An out-of-office rule can also reroute new requests while preserving the original chain record. Approval does not send a document for signature. After all required stages pass, use your configured e-signature integration and store the returned file as the Executed Copy. # Use the Clause Library The Clause Library is the Workspace source of truth for approved contract language. Each Clause includes a category, preferred text, optional fallback positions, owner, review date, and usage history. ## Find the right Clause Search by title, phrase, category, agreement type, or tag. Filters can narrow results to a legal entity, governing law, or active approval status. The preview shows where the Clause is already used and whether a newer version is available. Open the library from a draft Place the cursor where the language belongs, then select **Insert Clause**. Your Company keeps the draft visible while you search. Review context and fallback positions Read the drafting note and linked Playbook before inserting. A fallback is appropriate only when the negotiation facts match its stated conditions. Insert approved language Select **Insert preferred** or an allowed fallback. Your Company records the Clause identifier and version on the document. Handle later updates If the library owner publishes a material change, Matter owners can compare the new language with active drafts. Your Company never changes a draft silently. Use a Clause for reusable legal language and a Template for a complete agreement structure. Keeping these distinct makes updates easier to govern. Version 4.0 introduced usage analytics so Admins can identify heavily negotiated language and clauses that are rarely selected. See the [4.0 release notes](/release-notes/v4-0). # Renewals and reminders Your Company turns the Executed Copy into an active contract record. A Renewal Reminder alerts the assigned owner before an important date, especially a cancellation notice deadline or renewal decision date. ## Add a renewal schedule From an executed Matter, open **Dates and obligations**. Confirm the effective date, initial term, renewal type, renewal period, notice period, and final termination date when applicable. Choose the controlling date For automatic renewals, anchor reminders to the notice deadline. For fixed terms, anchor them to the expiration date unless the contract requires an earlier decision. Assign an owner Choose the Workspace member responsible for the commercial decision. Add legal or finance members as watchers when they need visibility but do not own the action. Set reminder timing Apply the Workspace default or choose custom intervals. Your Company supports multiple reminders and an escalation recipient if the owner does not acknowledge the first alert. Record the outcome Mark the contract as renewing, renegotiating, terminating, or complete. Starting a renegotiation creates a linked Matter while preserving the Executed Copy. A reminder supports your process but does not change or terminate a contract. Follow the notice method and delivery requirements in the Executed Copy. For older agreements, [import legacy contracts](/getting-started/importing-legacy-contracts) before creating renewal schedules. # Review a contract sent to you If a customer sends you a review link through Your Company, you can read and comment on the contract without a paid Workspace seat. The link is tied to your email address and one Matter. Open the secure link Select **Review contract** in the invitation email. If verification is required, enter the one-time code sent to the same address. You do not need to create a password. Check the document details Confirm the sending organization, Matter name, document version, and response deadline. Contact the sender if the parties or document are not what you expected. Read and comment Move through the document in your browser. Highlight text to add a comment. Your draft comments are visible only to you until you return the Turn. Return your response Select **Review response**, confirm your changes and comments, then select **Return Turn**. Your Company sends the Workspace owner a locked record of your response. Do not forward your review link. If another person should participate, ask the sender to invite that person directly so the Matter history identifies each reviewer. Review links can expire or be revoked by the sender. If the page says the link is no longer active, request a new invitation from the Matter owner. Need to edit the language itself? See [proposing changes](/counterparties/proposing-changes). # Propose changes as a counterparty Counterparty review lets you propose additions and deletions directly in the browser. Your edits become one Turn when you return them to the sender. ## Make a clear proposal Select text and choose **Replace**, **Delete**, or **Comment**. To add language, place the cursor and choose **Insert**. Your Company marks the proposal with your name and keeps the original text available for comparison. Edit the contract language Make one focused change at a time. Use a comment to explain the business reason or identify information the sender needs to supply. Review unresolved items The change list shows every edit and comment in your draft Turn. Resolve comments that were answered during your review and remove accidental changes. Check the clean preview Select **Preview if accepted** to read the document as it would appear if the sender accepted all proposals. This helps catch duplicate words, broken references, and inconsistent defined terms. Return the Turn Add an optional summary, then select **Return Turn**. You can continue reading the Matter, but you cannot alter that Turn after submission. Returning a Turn proposes language. It does not accept the contract or create a signature. The sender will review your changes and may return another Turn. If you cannot open the document, first review the steps for [account-free review links](/counterparties/reviewing-a-contract-sent-to-you). # Sign-in and SSO issues Workspace members sign in through their work email or the Workspace single sign-on connection. Counterparties using a review link should return to their invitation instead of using the member sign-in page. ## Start with these checks Confirm the Workspace address Use the Workspace URL from your invitation. If you belong to more than one Workspace, confirm that the name shown on the sign-in page is correct. Use the invited email Sign in with the exact address an Admin invited. Aliases and personal addresses are treated as different identities. Restart the session Close other Your Company tabs, open a private browser window, and try again. This clears stale sign-in state without changing saved browser data. ## Single sign-on messages - **Domain not assigned:** Ask a Workspace Admin to confirm that your email domain is connected to the Workspace. - **Access denied by identity provider:** Your account reached your organization's sign-in service, but that service did not authorize Your Company. Contact your internal access administrator. - **Invitation required:** Authentication succeeded, but you do not have a Workspace seat. Ask an Admin to [invite you](/getting-started/inviting-your-team). - **Session expired:** Begin again from the Workspace sign-in page rather than refreshing the error page. When contacting support, include the Workspace name, time of the attempt, your browser, and the error code. Do not send your password or a one-time verification code. If the issue persists, [contact Your Company Support](/support/contact-support). # Document upload errors Your Company accepts searchable PDF and DOCX documents up to 50 MB. An upload can fail when the file is protected, damaged, incomplete, or uses a format Your Company cannot process. The file type is not supported Save the contract as PDF or DOCX, then upload the new copy. Image files, archive files, and email attachments saved in proprietary container formats must be converted first. The document is password protected Open the file in your document application, remove password or editing protection, and save a new copy. Do not send the password to Your Company Support. No readable text was found The PDF may contain only scanned page images. Create a searchable PDF using optical character recognition, confirm that you can select its text, and try again. The upload stopped or timed out Confirm the file is below 50 MB and retry on a stable connection. If the document contains many high-resolution images, reduce their resolution without removing signature pages or exhibits. ## Before retrying Rename the file with ordinary letters, numbers, spaces, hyphens, or underscores. Open the saved copy from your computer to confirm it is complete. Then return to the Matter and select **Upload new version**. Do not split an Executed Copy merely to meet the size limit. Contact support so the complete signed record can be preserved as one controlling document. If a cleaned file still fails, [contact support](/support/contact-support) and include the error code, file type, file size, and Matter identifier. Do not email the contract unless Support provides a secure upload request. # Contact Your Company Support Workspace members can open **Help > Contact Support** in Your Company. This creates a secure ticket linked to the current Workspace. If you cannot sign in, email `support@your-company.example` from your invited work address. ## Support hours Standard support is available Monday through Friday, 6:00 a.m. to 6:00 p.m. Pacific Time, excluding published company holidays. Severity 1 incidents are monitored at all times for contracted production Workspaces. ## Severity levels | Severity | Use when | Initial response target | | --- | --- | --- | | 1, Critical | The production Workspace is unavailable, or active signature and negotiation work is broadly blocked. | 30 minutes | | 2, High | A core workflow is unavailable for multiple members with no reasonable workaround. | 2 business hours | | 3, Normal | A feature behaves incorrectly, but work can continue. | 1 business day | | 4, Question | You need product guidance or want to suggest an improvement. | 2 business days | Response targets indicate when investigation begins, not when an issue will be resolved. ## What to include - Workspace name and Matter identifier, if applicable - What you expected and what happened instead - Exact time of the most recent occurrence, including time zone - Browser and operating system - Error code and a screenshot with confidential contract text hidden - Steps that reliably reproduce the issue Never include passwords, API keys, one-time codes, or full contract documents in an email. Support will provide a secure upload request when a file is required. # Frequently asked questions How does Your Company protect contract data? Your Company encrypts network traffic and stored customer data, separates each Workspace logically, and records administrative and contract activity in an audit log. Admins can require single sign-on, manage session duration, restrict API keys, and revoke member or counterparty access. Security documentation and current independent assessment materials are available to customers through a secure review request. Where is Workspace data stored? A Workspace is assigned to one supported region at provisioning. Your Company currently offers United States and European Union regions. Primary data and backups remain in the selected region. Some outbound integrations process only the fields needed to complete the requested action; their locations depend on the provider your organization chooses. Who counts as a paid seat? Every active Workspace member with an Admin, Editor, Approver, or Viewer role counts as a seat. A person invited only through a counterparty review link does not count as a seat. Suspended members cannot sign in and do not count toward the active seat total after the current billing period is reconciled. Do counterparties need an account? No. A counterparty can open a secure, email-bound review link, verify access with a one-time code when required, propose changes, comment, and return a Turn without creating a paid account. The Matter owner controls link expiration and can revoke access at any time. Can we export our contracts and metadata? Yes. Admins can export Matter metadata, activity history, approval records, Clause Library content, and documents in commonly readable formats. An individual Matter export includes every document version, Turn summary, approval decision, and the Executed Copy. Large Workspace exports are prepared asynchronously and delivered through a time-limited secure link. How long does Your Company retain deleted information? Deleted Matters enter a 30-day recovery period before scheduled removal from active systems. Backups age out within 35 additional days. A Workspace can adopt a longer retention policy or place a Matter on legal hold. Closing a Workspace starts the contractual export and deletion process unless a legal obligation requires continued retention. Does Your Company replace our e-signature provider? No. Your Company prepares the approved document and sends it through your configured e-signature integration. When signing finishes, Your Company stores the returned file as the Executed Copy and records the completion event. Signature identity, delivery, and certificate behavior are governed by your chosen provider. Can Your Company manage more than one legal entity? Yes. Admins can configure multiple legal entities in one Workspace and limit Templates, Clauses, Playbooks, and Approval Chains by entity. Each Matter has one contracting entity, which determines the organization details and default rules inserted into the draft. What happens when a contract renews? A Renewal Reminder notifies the assigned owner before the configured notice deadline or renewal date. The owner records whether the agreement will renew, terminate, or enter renegotiation. Your Company does not send termination notice automatically. A renegotiation creates a linked Matter while the prior Executed Copy remains unchanged. Still need help? [Contact Your Company Support](/support/contact-support) from your Workspace. # Your Company 4.2 **Released May 21, 2026** Version 4.2 brings Playbook guidance into the redlining workspace. Reviewers can compare a proposed term with the preferred position, see approved fallbacks, and identify escalation rules without leaving the active Turn. ## Added - Playbook suggestions beside supported clauses during review - One-click insertion of an approved fallback position - Deal-context checks for value, term, governing law, and agreement type - A reason field when a reviewer proceeds outside Playbook guidance ## Improved - Change groups now keep rewritten sentences together for a single accept or reject decision - Clause suggestions show the current Clause Library owner and review date - Matter activity identifies which Playbook version informed a completed Turn - Clean preview loads earlier while large documents are still processing comments ## Fixed - Resolved an issue where a moved comment could remain attached to deleted text - Corrected section numbering after accepting multiple nearby insertions - Prevented duplicate reviewer notifications when a Turn was returned near its deadline Playbook suggestions are guidance, not automatic decisions. Your Workspace controls the approved positions and escalation rules shown to reviewers. Learn how to use suggestions in [redlining basics](/contracts/redlining-basics). # Your Company 4.1 **Released March 12, 2026** Version 4.1 makes Approval Chains more resilient. Approvers can delegate responsibility for a defined period, and Admins can configure an out-of-office reroute for new requests. ## Added - Time-bounded approval delegation to another eligible Workspace member - Out-of-office rerouting for requests created during an absence - A delegation history showing the original approver, substitute, reason, and dates - Admin controls that restrict which approval stages may be delegated ## Improved - Approval reminders now account for the active delegate and local business hours - Matter owners can see upcoming approver absences before submitting a request - Reassigned approval emails include the decision summary and attached document version - Approval exports distinguish direct, delegated, and rerouted decisions ## Fixed - Prevented a completed stage from reopening when an approver's role changed - Corrected overdue labels for requests paused by a Workspace holiday - Resolved an occasional mismatch between the approval panel and Matter activity history Delegation changes who can decide. It does not change the Approval Chain definition or erase the originally assigned approver. See [Approval Chains](/contracts/approval-chains) for routing behavior and decision records. # Your Company 4.0 **Released January 28, 2026** Version 4.0 introduces a new Clause Library built for governed reuse. Legal operations teams can publish preferred language, manage fallback positions, and understand how clauses perform across active negotiations. ## Added - Clause version history with owner, approval status, and effective date - Usage analytics by agreement type, legal entity, and negotiation outcome - Preferred and fallback positions stored together with drafting guidance - Filters for governing law, risk category, language, and review status - Impact review for active drafts that contain an older Clause version ## Improved - Search now matches defined terms and phrases within Clause text - Template editors can pin a Clause to the latest approved version or a specific version - Clause insertion records the identifier and version in Matter activity - Bulk import reports invalid metadata before publishing any content ## Fixed - Preserved paragraph formatting when inserting a Clause into a numbered list - Corrected duplicate results caused by overlapping category and tag filters - Prevented retired Clauses from appearing as preferred suggestions in new Matters Existing library entries were migrated as version 1 and retained their prior titles and categories. Admins should assign owners and review dates after upgrading. Learn how editors use the redesigned [Clause Library](/contracts/clause-library). # Developer overview Your Company API lets your systems create and track Matters, upload documents, record negotiation Turns, query Clauses, request approvals, and manage webhook subscriptions. ## What you can build Matter intake Create a Matter from an approved request in your CRM, procurement system, or internal portal. Contract archive Synchronize Executed Copies and selected metadata with your records repository. Approval automation Request an Approval Chain when a commercial threshold or policy rule is met. Event-driven workflows React when a Turn completes, an approval is requested, or a Matter is executed. ## Base URL All version 1 endpoints begin with: ```text https://api.your-company.example/v1 ``` Requests and responses use JSON except document upload and download operations. Identifiers have a resource prefix, such as `mat_` for a Matter and `doc_` for a document. List endpoints use opaque cursor pagination. API access is scoped to one Workspace. Create separate credentials for development and production Workspaces so test data cannot enter a live contract record. Start with [authentication](/developers/authentication), then use the [API Reference](/api-reference/overview) for endpoint details. # Authentication Your Company API uses bearer authentication. An Admin creates an API key under **Settings > Developer settings > API keys** and chooses the permissions it needs. ## Send the key Include the secret in the `Authorization` header on every request: ```http GET /v1/matters?limit=20 HTTP/1.1 Host: api.your-company.example Authorization: Bearer rlk_live_•••••••••••• Accept: application/json ``` The full secret is shown once. Store it in your deployment's secret manager and inject it at runtime. Do not place a key in browser code, source files, support tickets, or request logs. ## Workspace scoping Each key belongs to exactly one Workspace. A request can access only resources in that Workspace, even if your organization operates several Workspaces. Create and rotate a separate key for each integration and environment. Permissions are resource and action based. For example, an intake integration might need `matters:write` and `documents:write`, while an archive job needs `matters:read` and `documents:read`. Your Company never asks for an API key through email. If a key may have been exposed, revoke it immediately, create a replacement, and review the API audit log. ## Authentication errors - `401 unauthorized` means the key is missing, malformed, expired, or revoked. - `403 forbidden` means the key is valid but lacks the required permission. - `404 not_found` can mean the resource exists in a different Workspace. Next, configure [webhooks](/developers/webhooks) for changes you need to receive without polling. # Webhooks Webhooks send an HTTP POST request when activity occurs in your Workspace. Create a subscription for only the event types your integration needs. Common events include: - `matter.turn_completed` when either side returns a completed Turn - `matter.executed` when an Executed Copy is stored - `approval.requested` when an Approval Chain reaches a new stage - `approval.decided` when an approver records a decision ## Delivery and retries Return a success status within five seconds after validating and storing the event. Process slow work asynchronously. If delivery fails or times out, Your Company retries after 1 minute, 5 minutes, 30 minutes, 2 hours, and 12 hours. A subscription is paused after 20 consecutive failed deliveries. Events can arrive more than once and, during retries, out of order. Use the event `id` for deduplication and the `created_at` time for ordering within one resource. ## Verify a signature Each request includes `YourCompany-Webhook-Id`, `YourCompany-Webhook-Timestamp`, and `YourCompany-Webhook-Signature` headers. Build the signed content from the identifier, timestamp, and exact request body, separated by periods. Compute an HMAC-SHA256 digest with the subscription secret and compare it with the supplied signature using a constant-time comparison. Reject timestamps more than five minutes from your server time to reduce replay risk. Verify the signature before parsing or acting on the payload. Return success for an event you have already processed. Use the [webhook subscription endpoints](/api-reference/get-webhook-subscriptions) to create and manage destinations. # API Reference Your Company API provides Workspace-scoped access to Matters, documents, Turns, Clauses, approvals, and webhook subscriptions. ## Conventions - Base URL: `https://api.your-company.example/v1` - Authentication: bearer API key on every request - Request and response bodies: JSON, except binary document operations - Timestamps: ISO 8601 in Coordinated Universal Time - Pagination: `limit` plus an opaque `cursor` - Errors: a stable `code`, human-readable `message`, and request identifier Resource identifiers are stable strings with prefixes such as `mat_`, `doc_`, `trn_`, `cls_`, `apr_`, and `whs_`. Treat identifiers and pagination cursors as opaque values. Start with the [developer overview](/developers/overview) and [authentication guide](/developers/authentication) before making your first request. Select an operation in the API Reference navigation to see its parameters, request body, response schema, and example.