Help Contents | VPC Sign On | Welcome Page | Tree View | Open/Save Screen | Check-out | Check-in | History | Copy to Local | Add | Search (document) | Search (attributes) | Search (document attributes) | Entering and Editing Data in a Table | Workplan | Calendar | Pending Action Items/Tasks | Notification | Action Items | Email Table | User Broadcast | User File Merge | User Document Merge | Attributes (proposal) | Attributes (general) | Team Members | User Profile | Dashboard
Administrator Log On | Set Up | Copy to Local | Permissions | Groups | Admin. Workplan | Admin. Notification | Admin. Calendar | Admin. Action Items | Admin. Email Table | Admin.Search (document) | Admin. Search (attributes) | Admin. Search (document attributes) | Admin. History | File Merge | Document Merge | Admin. Attributes (proposal) | Admin. Attributes (general) | Admin. Attributes (document) | Banner Message | Broadcast Message | Users | Zone | Glossary (Definitions)


Establishes the level(s) of access allowed for each user or group to proposals, folders and/or individual documents. A user with higher level permissions also has all lower level permissions on a given folder or document. Permissions are inherited from higher level folders unless specifically set differently at a lower level folder/file.

The access levels include:

  • Read - can download files and links to use as desired, but not change server copy
  • Review - can check out a file for review
  • Edit - can change the document and create a new version
  • Create - can add new files and URL links in a folder, or add a new folder
  • Delete - can delete files and links from a folder

Permission checking uses the following rules for any given document (in order of precedence):

  • check for permission specifically set for that document for the user or group of which user is member;
  • if no permission is found, continue checking up the folder hierarchy until a permission is found;
  • if for a document or folder, there are conflicting permissions, then highest permission level will hold. Note: when an individual permission is set on a node, the permission set on the same node at a group level is removed. When a group level permission is set on a node, the individual permission set on the same node is preserved. So the order in which it is done matters. Only in the latter case is there a possibility of conflicting permissions existing.
  • if neither of the above applies (no explicitly assigned permissions), then use the default (system-wide) permission set by the system administrator

See "Assigning Permissions" below the screen shot.

User Settings

These checkboxes control various functions users may do. If checked, the user can perform that function. If unchecked, it will not be available to them.

  • Display to Team: Be visible in Team Members view.
  • Edit Action Items: Access most Action Item functions on user side.
  • Show Version: See version folders.
  • Rename Files: Edit file names on user side (with Create permission or higher).
  • Edit Workplan: Edit Workplan, Notifications and Calendar periodic events on user side.
  • Edit Folder Activity: Allows user to set Document Status in Folder Activity Report.
  • Edit Prop Banner: Allows user to edit the Proposal Banner from user side.
  • Broadcast From User Side: Send broadcast messages from user side.
  • Requestor Status: Allows user to generate user account requests.
  • Merge Docs From User Side: Allows user to merge documents from user side..

Assigning Permissions

    To assign permissions for this proposal to specific users or groups, first select the group or user from the list, then the folder, file or link from the treeview, then select the permission type from the Permissions list. Permission can be set on folder links, but any permission above read only will be interpreted as read only. Folder links inherit permissions, just like regular folders. When the users panel is selected and you hit a letter key, the list will scroll to the user name beginning with that letter. Use the Shift key for continuous selection of users/groups/folders/files. Use the Ctrl key for multiple individual selections of users/groups/folders/files. Use Ctrl -A key to select all users or all groups.

    The color of the folder in the treeview and the button will change to match the color of the permission in the list, indicating that the specified permission has been assigned for that folder, file or link to that user or group. Select a node and user(s)/group(s) and click on applicable, colored, activated permission button to clear permissions specifically set on that node for selected user(s)/group(s). To copy permissions from one node to another node, right click on the source node and select Copy Permissions. Right click on the target node and select the now-activated Paste Permissions. This will only copy permissions specifically set on the node and will not override subfolder permissions.

    The icons on the top right give the ability to:
    • copy permissions from a user or group to other users and/or groups. Select user or group, click on copy permissions icon, and then select the targets from the panel that opens. Can also choose to copy proposal rights (e.g., Display to Team, Edit Workplan, etc.) to the target user. Only users who have been designated as "Available" in that zone will show in the Users box.
    • clear proposal access for selected users and groups.
    • show users with proposal access along with users' admin status and expiration date for third party users. Admins that are blocked from the proposal will still show as an admin but will be displayed with an "*" in the admin column.
    • clear permissions explicitly set for selected users and groups. Can also clear group-based permissions for selected users.
    • show the daily report subscribers.
    • show the active users along with their highest permission level.
    • show all permissions explicitly set for a single node.

    To temporarily disable check-out for edit or review for all users without changing their permission settings, select a folder in tree view, and then click on Disable Check-out. This works like permissions in that check-out disable is inherited from top-level folders. Folders/files that have check-out disabled will show in italics in permissions tree view. The check box will turn blue if the selected folder/file has check-out disabled, but it is inherited from higher-level folder. If a folder selected for disable check-out has a file within it that is checked out for edit, a warning panel will appear with an option to cancel action.

    You can modify various settings for a particular user or group. Display to Team determines whether a user or group is displayed in the Team Member list on the user side. Edit Action Items can allow a user or group to fully edit, add, delete, and export action items on the user side. Rename Files allows a user or group to edit file names on the user side given they also have create permission. They can only rename files from the Add Document to VPC screen. Select user or group and uncheck Show Version if you do not want a user or group to see version folders for that specific proposal. Edit Workplan can allow a user to edit the workplan with full capabilities on the user side. Edit Folder Activity allows a user to set a document's status in the Folder Activity Report on the user side. Edit Prop Banner allows a user to edit the Proposal Banner on the user side. Broadcast From User Side allows a user to send broadcast messages from the user side, though Send Proposal Welcome is not enabled. Requestor Status allows a user to generate requests to add users to the proposal, to change group membership for users in the proposal and other miscellaneous things.

Back to top

© 1997-2015 Intravation, Inc.