--- url: https://docs.codefox.ai/apps/corsac/set-up-for-your-team.md --- # Set up Corsac for your team This page lets a person who can manage Corsac set it up for the company: the signing policy, the seal certificate, who can use Corsac, what signers see, and the keys other systems use. People who can use Corsac see only **Sharing** under settings. ## Before you start * You can manage Corsac. When Corsac is connected to Foxden Admin, the Owner gives you that level in Admin (see [Give people access to the apps](/run-your-company/people)). * Email set up on the server, so invitations and signing codes reach people (see [Set up email](/self-host/email)). The settings are in the sidebar, in two parts: **Workspace** (**Signing**, **People**, **Company**, **Sharing**) and **Server** (**API keys**, **Webhooks**, **Jobs**, and **Updates** when Corsac runs alone). ## Set the signing policy 1. Open **Signing**. 2. Under **Policy**, set: * **Timestamp authorities**: the addresses Corsac asks for a trusted timestamp, one per line, tried in order. A new install uses DigiCert, then Sectigo. Keep at least one. * **Days between reminders**: how often a signer who has not finished is reminded. `0` turns reminders off. The default is 3. * **Reminders per signer**: the most any one signer is sent. The default is 5. * **Retention (years)**: from 1 to 30, 7 by default. This is the period you declare in your policy; Corsac does not delete documents by itself. 3. Select **Save settings**. The reminder settings are the defaults for new documents. A sender can change them for one document in **Review and send**. ### Decide what reaches Library The Library section of the **Signing** page sets what reaches Library. Nothing is filed until Library is paired with Corsac on your server. * Who sees signed documents in Library rooms: **Its recipients** (a room visitor whose address a code proved is one of the document's recipients), **Any verified visitor**, or **Never**. A private or unfinished document is never shown in a room. * Which signed documents are filed in Library: **None**, **Documents made for a room or a deal** (one a Library room sent for signature, or one Fennec drew for a deal), or **Every signed document**. A filed copy is the signed PDF, kept in Corsac's space in Library, where Library's managers can read it. Private documents are never filed. ## Use your own seal certificate Corsac makes its own seal certificate the first time it needs one. It is self-signed, valid for 10 years, and named after your company: ` via Corsac Sign`. The company name in it is the one set on the server when Foxden was installed (the server setting `ORG_NAME`), as it was at that moment. Changing the company name later, in Corsac or in Admin, does not change a certificate already made. To have the seal chain to a certificate authority, or to correct the name, import a certificate: 1. Open **Signing** and go to **Seal certificate**. 2. Choose the **PKCS#12 file (.p12 / .pfx)**. It must allow signing. 3. Type its **Passphrase**. 4. Select **Import and rotate**. The new certificate seals every document from then on. The old one moves to **Retired** under **Certificates** and is kept, so documents sealed with it still verify. Every fingerprint, old and new, is published on your server at `/.well-known/corsac-seal`. ## Manage people When Admin manages people, **People** takes you to Admin, where the Owner invites people and sets their level for each app. See [Give people access to the apps](/run-your-company/people). When Corsac manages its own people: 1. Open **People**. 2. Under **Invite someone**, type the **Email address**. 3. Choose the **Level**. 4. Select **Send invitation**. The link in it works for 7 days. To change someone later, open their menu in the **Members** list and select **Let them manage**, **Can use only**, **Deactivate** or **Reactivate**. While mail is off, the invitation is not emailed: Corsac shows the link once, and you send it yourself. The last person who can manage Corsac cannot lose that level; give it to someone else first. ## Set what signers see Open **Company**. * **Name**: the company's name. When Admin is connected it comes from **Workspace** › **Company** in Admin (see [Your company's name and brand](/run-your-company/company)); otherwise it is set on the server. * **Branding**: what signers see in the invitation, reminder and completion emails, on the signing page and on the verify page: * **Display name**, shown to signers and in their emails; * **Logo**, a PNG or JPEG up to 512 KB and 2000 px a side; * **Accent colour**, for buttons and links (Corsac darkens a colour that white text cannot be read on); * **Support email**, offered to signers as who to ask if something looks wrong; * **Email footer line**, such as a company registration. With Admin connected, a field you leave empty uses the company's logo, colour and support address from Admin. Branding never changes the sealed PDF or the certificate of completion, and **Powered by Corsac** stays on signer pages. * **Embedding the signing page**: under **Allowed origins**, the websites allowed to show the signing page inside their own app, one per line, such as `https://app.example.com`. Blank means no site may. See [Embed the apps](/connect/embed). ## Choose the default sharing 1. Open **Sharing**. 2. Under **Default sharing**, choose where new documents start: **Private**, **Share with managers only** (the default) or **Share with members**. 3. Select **Save changes**. Each document's owner can change its level afterwards. Anyone who can open a document through its level can also send, void or delete it, so the default decides who can act on new documents as well as who can see them. See [Track and manage documents](/apps/corsac/track-and-manage) and [Sharing](/run-your-company/sharing). ## Connect other systems * **API keys**: under **Create a key**, give the key a **Label**, a **Scope** (**Read-only (GET requests)** or **Full access (create, send, void, manage webhooks)**) and an **Expires** date. The key is shown once. A key acts as the person who made it and reaches that person's own documents and templates; it stops working if they are deactivated. **Keys for agents** makes a key for an agent user. See [Use the Corsac API](/connect/corsac-api). * **Webhooks**: under **Register an endpoint**, give a public `https` address and choose the events it is sent. Open an endpoint to see its delivery attempts. See [Use the Corsac API](/connect/corsac-api). * **Jobs**: the background work (sealing, mail, reminders, webhooks). Select **Retry** on a job that failed. AI assistants reach Corsac through Admin, not through these keys: see [Connect your AI assistant](/connect/ai-assistant). ## What is set in Admin instead When Corsac is connected to Admin: * sign-in goes through Admin (see [Sign-in](/run-your-company/sign-in)); * people and their levels are managed in Admin, when the server is set up for it; * the company name comes from Admin, and so do the logo, colour and support address unless you fill them in here; * updates are in Admin, under **Server** › **Products**; * Corsac's activity appears in Admin's activity log (see [Activity](/run-your-company/activity)). The signing policy, the seal certificate, branding overrides, embedding, sharing, API keys and webhooks stay in Corsac. Every server setting is listed in [Corsac settings](/reference/settings/corsac). ## Troubleshooting ### The seal certificate will not import * **Could not read this P12**: the passphrase is wrong, or the file is not a PKCS#12 bundle. * **This P12 carries no certificate and private key pair**: export the bundle again with its private key. * **This certificate is already installed**: it is the one in use, or a retired one. ### Signers see the wrong company name in the seal The certificate was made with the name the server had when it first needed one. Import a certificate with the right name, as above. ### Documents are sealed without a trusted timestamp The server could not reach any timestamp authority. Timestamp authorities are called over `http`, so a firewall that blocks outgoing `http` stops them. Ask whoever runs the server to allow it, or list authorities it can reach.