Security Scenarios and Best Practices¶

Follow this guide when setting up infoRouter security for the first time or creating new libraries.

Security Implementation Steps¶

Step 1: Create Users¶

Create user accounts from the Control Panel.

Action	Location
Create users	Control Panel → Manage Users

Creating Users

Step 2: Create Global User Groups (Optional)¶

Global groups simplify library membership assignment.

Action	Location
Create global groups	Control Panel → Global User Groups

User Groups

Step 3: Create Libraries¶

Create libraries for different functional areas:

Library Example	Purpose
Accounting	Financial documents
Marketing	Campaign materials
Sales	Proposals and contracts
Human Resources	HR policies and records

Library Isolation

Libraries are isolated work areas. Non-members cannot see or access library content.

Creating Libraries

Step 4: Assign Library Members¶

Add users and groups as library members.

Step 5: Create Local Users (Optional)¶

For users who only need access to one library, create them as local users.

Users Overview

Step 6: Create Local User Groups¶

Best Practice

Local user groups are essential for good security:

Assign security to groups, not individuals
When users change roles, simply update group membership
Revoke access by removing from group

Local User Groups

Step 7: Create Folder Structure¶

Design your folder hierarchy to match your workflow.

Guideline	Recommendation
Depth	Maximum 6-7 levels
Names	Descriptive but not too long
Path length	Keep under 250 characters total

Path Limitations

File system exports are limited to 250 characters for the full path including document name.

Creating Folders

Step 8: Assign Folder Security¶

Recommendation	Details
Plan first	Think through your security structure
Minimize Full Control	Use minimum necessary permissions
"Add" permission	Allows users to create and access their own documents

Folder Security

Step 9: Assign Document Security¶

Best Practice	Benefit
Use groups	Easier to manage than individual assignments
Role-based	Access follows job function
Easy revocation	Remove from group to remove access

Document Security

Summary: Security Best Practices¶

Practice	Why
Use groups	Easier management, cleaner revocation
Minimum permissions	Reduce risk, follow least-privilege
Plan folder structure	Reflects workflow, supports security
Test access	Verify before going live