Viewing Another Team Member's Work
To view or edit another team member's work in FLK it over, you must first be granted permission by an Admin or Principal user.
Regular users cannot grant these permissions.
Granting Access to Team Members
As an Admin or Principal, you can control which users can view and edit other team members' documents. Admins, however, cannot view or edit other users' documents unless they are explicitly granted permission.
Role-Based Permissions
Agency Principal: Full access to all settings and documents.
Admin: Similar to Principals but cannot view/edit other users’ documents unless granted permission.
Team Member: Limited to their own documents unless permissions are granted by an Admin or Principal.
Step 1: Open Team Settings
Click your profile name in the top-right corner of FLK it over.
Select Settings from the dropdown menu.
Click Team from the menu on the left-hand side.
Step 2: Select the Team Member
Locate and select the team member you would like to grant permissions to.
Open their user settings.
Step 3: Choose Access Permissions
You can grant access in one of two ways:
Grant Access to Specific Team Members
Tick the checkbox next to the name of each team member whose work they should be able to view and edit.
Grant Access to All Team Members
Scroll to the bottom of the permissions section and select the option to allow the user to view and edit all team members' work.
This is useful for managers, administrators, or team leaders who require broader visibility across the business.
Step 4: Save Your Changes
Once you have selected the appropriate permissions, click Save at the bottom of the page.
The team member will now be able to view and edit the work of the users you have assigned access to.
Important Note
Granting access allows the selected user to both view and edit the assigned team members' documents. Consider your agency's internal processes and privacy requirements when assigning permissions.
To restrict access, assign the user a Team Member or Admin role without granting additional permissions, and avoid enabling "Two-Way Access" or similar settings.