Skip to main content

View & Edit Contract Followers

Learn how to manage default followers for each contract template, ensuring the right people receive notifications and have access to the contracts they need to track.

Written by Akshat Singhal

Overview

The Contract Followers setting lets you define and manage the default followers for each contract template. Followers are users in your organisation who are assigned to a contract template and, depending on their access rights, can view, edit, and receive notifications at each stage of the contract. They can also view and manage the contracts they are following directly from their repository.

How to Access Contract Followers

1. Click on Settings from the left-hand navigation bar.

2. Click on User Management.

3. Select the Contract Followers tab.

This opens the Contract Followers page, which displays all contract templates alongside their assigned default followers.

Filtering and Searching

At the top right of the page, you can:

  • Filter by users: use the dropdown to filter the template list by a specific user

  • Search by template name: use the search bar to find a specific contract template quickly

Viewing Followers

Each template row displays the Default Followers assigned to it as avatar icons. If no followers have been assigned, the column shows N/A.

Click the View (eye) icon in the Actions column to see the full list of followers assigned to a specific template.

Editing Followers

Click the Edit (pencil) icon in the Actions column to update the followers for a template.

  • Select users from your organisation to add as followers

  • Remove existing followers by deselecting them

  • Click Save to apply the changes, or Cancel to discard them

Conclusion

Keeping default followers up to date on each template ensures that the right team members are automatically notified and given access whenever a contract is initiated from that template. Regularly reviewing follower assignments, especially when team structures change, prevents contracts from going unmonitored and keeps everyone who needs visibility in the loop.

Did this answer your question?