Skip to content

Library Usage Scenarios

Plan your infoRouter library structure based on organizational needs and use cases.


Typical Corporate Library Layout

A typical organization might create libraries for:

Department Library Purpose
Accounting Financial documents, invoices, reports
Sales Proposals, contracts, quotes
Marketing Campaigns, collateral, brand assets
Human Resources Policies, employee records, forms
Information Services Technical documentation, procedures
Customer Service Support guides, FAQs
Help Desk Tickets, knowledge base articles

Why Have Multiple Libraries?

Separation of Concerns

Each department typically has its own policies, procedures, and security requirements. Separate libraries allow:

  • Different retention policies per department
  • Unique security settings for sensitive data
  • Separate audit trails for compliance
  • Custom workflows for each business area

Common Library Use Cases

Private Work Areas

Use Case Description
Departmental HR department library visible only to HR staff
Project-based Project teams with isolated workspace
Legal Sensitive contracts requiring separation

External Access

Use Case Description
Customer portal Clients access their documents
Partner sharing Vendors and partners collaboration
Public content Announcements and forms

Anonymous Libraries

Anonymous libraries are accessible to all infoRouter users without membership.

How They Work

Permission Behavior
Default access READ for all users
Higher permissions Can be granted for specific users
No membership required Everyone can view

Anonymous Library Uses

Use Case Examples
Announcements Company news, policy updates
Public forms Vacation requests, expense reports
Corporate info Vision, locations, org charts

Multi-Library Membership

Flexible Access

Users can belong to multiple libraries. A project manager might be a member of:

  • Project Management library
  • Accounting library (for budgets)
  • Marketing library (for campaigns)

Best Practices

Practice Benefit
Organize by function Match business structure
Use consistent naming Easy navigation
Plan permissions early Avoid security gaps
Consider growth Allow for expansion

See Also