COBBLESTONE SOFTWARE

Contract Insight — User Guide

File Restriction on Vendor Records

03. Admin User Manual › Vendor/Customer Management › File Restriction on Vendor Records

Note: Each procedure in this guide begins at the Contract Insight homepage, so any section can be followed on its own. Custom fields are configurable, so the exact field list on a contract category record may vary between environments.

1. Overview

This session did not surface a dedicated, per-attachment restriction toggle directly on a vendor/customer record's Attachments & Templates tab — the row-level actions available there (Download, an "Edit with VISDOM" shortcut, and file-type/version detail) did not include a distinct security or access-restriction control. The closest confirmed live equivalent is group-level, not per-file: a Security Group's Fields and Related records tabs (see "Security Groups") can restrict which groups of employees can see or edit a vendor record's fields and related sub-grids at all, which in effect restricts access to any attachments filed under those sections for members outside the group. Anyone extending this documentation should re-verify directly against a vendor record with an active file-restriction rule already configured, since none was found in this QA environment's sampled data.

2. Key Elements

A sampled vendor/customer record's Attachments & Templates tab showed Download and an "Edit with VISDOM" action per file, but no distinct per-attachment restriction or access-control toggle was found in this session's testing.
The nearest confirmed live control over who can see a vendor record's attachments is at the Security Group level: a group's Fields and Related records tabs (Administration > Security Groups) can restrict a group's visibility into parts of a vendor record, which indirectly limits access to file sections outside a permitted group's scope.
Manage User Permissions' Rules & conditions builder (see "View Permissions by Record") can also scope a Vendors/Customers-area permission to a subset of records, which would apply to that record's attachments along with everything else on it.
Because no explicit file-level restriction control was located on the vendor record itself, this topic should be re-verified against a vendor record that already has file-level restrictions configured, or by consulting current release notes for this feature.

3. Quick Reference Summary

[TODO: content needed]