## Internal portals — a public page of workflows

An internal portal is a simple, publicly accessible page that displays a list of your workflows as clickable links. No login is required to reach this page. It is useful when you want colleagues or clients to browse and select from a set of workflows without creating an account. You build an internal portal by creating a special workflow that contains only a **Kickout Page** formatted as a link menu.

1. **Create a new workflow**  
   From your Dashboard, click **New Workflow** and give it a name that reflects its purpose — for example, “Client Resources” or “Self-Service Documents.”

2. **Add a Kickout Page question**  
   Inside the workflow builder, add a **Kickout Page** question. This page will be the landing screen users see immediately — no questionnaire questions precede it.

3. **Add your workflow links**  
   In the body of the Kickout Page, add links to your other workflows using standard Markdown link syntax:
   
   ```
   [Text you want to appear](workflow link URL)
   ```  
   You can add as many links as you like. You can also embed images, videos, or introductory paragraphs to give the page more context.

4. **Save and publish**  
   Click **Save and Run**. Gavel generates a URL for this page. Copy it from the Dashboard using the three-dot menu ( **Copy workflow link**) and share it with your clients or embed it on your website.

If you want this portal page to be the default landing screen when someone visits `yoursubdomain.gavel.io`, email [help@gavel.io](mailto:help@gavel.io) and the team will configure it for you.

## Client portals — login-gated, personalized access

A client portal requires the user to sign in before seeing any workflows. Once logged in, each user sees only the specific workflows or bundles you’ve assigned to them. Their answers are saved to their account, so they can return and pick up where they left off.

### Requiring login on a workflow

1. **Open Access Permissions**  
   Go to the **Settings** tab of a workflow, then click **Access Permissions**.

2. **Set access to login-required**  
   Change the setting from **Anyone with Link** to **Only Logged-In Users** and save. You can optionally further restrict access to:
   * Specific email addresses only
   * Any email address belonging to a specific domain (e.g., everyone at `@yourclientfirm.com`)

3. **Optionally limit to one completion**  
   Enable **Allow each user to complete this workflow only once** if you want to prevent users from editing their session after generating documents or reaching the end of the workflow.

When a client clicks a login-required workflow link for the first time, they are taken to your Gavel sign-in page and prompted to create an account. Once they sign in, the workflow appears in their portal.

## Assigning workflows to specific users

Admin and Builder users can push specific workflows directly into a user’s portal, rather than relying on the user to discover the link themselves. The assigned user receives an email notification and sees the workflow in the **My Workflows** section of their dashboard.

1. **Find the workflow**  
   On the Dashboard, locate the workflow you want to assign.

2. **Open the assign menu**  
   Click the **three dots** (⋯) next to the workflow name and select **Share data entry only version**.

3. **Select assignees**  
   In the dialog that opens, choose the users from the dropdown and click **Assign Workflow**. The selected users are notified by email.

4. **Revoke access when needed**  
   To remove a user’s access, open the same **Assign Workflow** dialog and click the **×** next to the user’s name.

Assigned workflows remain in the user’s portal until you explicitly revoke access — they are not automatically removed after the user completes them.

## Access permissions reference

The table below summarizes how the access permission settings work:

| Setting | Who can access |
| --- | --- |
| **Anyone with Link** (default) | Any person who has the URL — no account required |
| **Only Logged-In Users** | Any person who creates a Gavel account and signs in |
| **Specific email addresses** | Only users whose exact email address is on the allow-list |
| **Specific email domain** | Any user whose email belongs to that domain (e.g., `@clientfirm.com`) |

If a workflow contains a Clio integration question or a CSV data source set to **private**, only users with Builder privileges can access it. If you see an “Unauthorized” message when sharing such a workflow, either set the CSV to public or grant Builder access to those users.

## Multiple signatures

When a generated document needs signature lines for multiple parties — such as all members of an LLC or all signatories to an agreement — you can automate this using a **Repeating Item** question.

### Setting up repeating signature lines

1. **Create a Repeating Item question**  
   In your workflow, add a **Repeating Item** question for the signatories (e.g., item name: `Members`, attribute name: `MemberName`).

2. **Insert the variable in a table in your Word template**  
   In your Word document template, insert the repeating variable inside a **table** using the Word add-in. Select the item as a repeating item and choose **Table** as the formatting. Adding a line immediately above the variable in the table creates a signature line above each name. Make the table borders **clear (no borders)** so that the final document shows only the underline and the name — not a visible grid.

3. **Test with different numbers of signatories**  
   Run the workflow and enter one member, then run it again with several members. Each signatory will appear on their own row with their own signature line.

### Two signatories side by side

If you want signatures to appear in two columns (odd entries on the left, even entries on the right), Gavel supports a special two-column table syntax in the Word add-in. Use `ItemName` for the Repeating Item name and `ItemAttributeName` for the attribute name inside that item.

Setting up signature tables is easiest when the table borders are removed after you’ve confirmed the layout looks correct. Use Word’s **No Border** table style to hide the grid.