TheVoĉoTheVoĉo
Configuration

Client Permissions

Purpose

Restrict user access to specific menus, features, and settings within Linkus clients.

Permission Types

Menu Visibility

Control which menus users can access

Operation Permissions

Control what actions users can perform

Extension Visibility

Control which extensions users can see

Contact Visibility

Control which contacts users can access


Purpose

Hide menus from specific users or groups.

Available Menus

  • Dial Pad: Make calls, access voicemail, dial extensions
  • Contacts: View company contacts, manage personal contacts, access phonebooks
  • Call History: View call logs, return calls, access recordings
  • Voicemail: Listen to messages, manage voicemail, configure greetings
  • Messaging: Team chat, SMS messages, file sharing
  • Meetings: Video conferencing, screen sharing, schedule meetings
  • Settings: Configure preferences, audio/video devices, notification settings

Configuration

Go to Client Permission > Menu Visibility

Create or Edit Rule

Create new rule or edit existing

Select Target

Select user/group to apply rule

Configure Visibility

Check menus to show, uncheck to hide

Save

Click Save to apply changes

Result

Users only see permitted menus in Linkus clients.

Use Cases: Hide voicemail for reception staff, hide messaging for basic users, hide settings to prevent misconfiguration.


Operation Permissions

Purpose

Restrict specific actions within menus.

Call Control

  • Call Recording: Allow/deny user to start/stop recording
  • Call Transfer: Allow/deny call transfer capability
  • Call Forward: Allow/deny forwarding rule configuration
  • Conference Calls: Allow/deny creating 3-way calls

Contact Management

  • Add Contacts: Allow/deny adding new contacts
  • Edit Contacts: Allow/deny modifying contacts
  • Delete Contacts: Allow/deny removing contacts
  • Export Contacts: Allow/deny exporting contact list

User Settings

  • Change Audio Settings: Allow/deny audio device modification
  • Modify Presence: Allow/deny status changes
  • Configure Notifications: Allow/deny notification preferences

Configuration

Go to Client Permission > Operations

Create New Rule

Create new permission rule

Select Targets

Select target users/groups

Configure Operations

Enable/disable specific operations

Save

Click Save to apply

Result

Users can only perform permitted actions.

Use Cases: Prevent users from disabling call recording for compliance, restrict contact editing to managers, lock audio settings for call center agents.


Extension Visibility Permission

Purpose

Control which extensions appear in directory and BLF lists.

Visibility Rules

Default Behavior

All users see all extensions.

Restriction Options:

  • By Group: Sales team only sees Sales extensions, each department sees own department
  • By Role: Executives hidden from general directory, managers see all staff see own team
  • By Department: IT team visible only to admins, reception sees everyone

Configuration

Go to Client Permission > Extension Visibility

Add Rule

Click Add Rule and enter descriptive name (e.g., "Sales Team Visibility")

Apply To

Select users/groups affected by rule

Configure Visibility

  • Show Extensions: Select which extensions are visible
  • Hide Extensions: Select which extensions to hide

Save

Click Save to apply rule

Result

Users only see permitted extensions in Linkus directory, presence, and BLF.

Use Cases: Privacy for executives, department segregation, multi-tenant deployment.


Contact Visibility Permission

Purpose

Control access to company contacts and phonebooks.

Contact Types

  • Always visible only to owner
  • Cannot be shared or restricted
  • Stored per-user
  • Shared contacts for organization
  • Visibility controlled by admin
  • Stored centrally

Phonebook Permissions

Permission Levels

  • View Only: User can see contacts, cannot add/edit/delete, can call contacts
  • Manage: Full CRUD operations - add, edit, delete contacts
  • No Access: Phonebook hidden from user, cannot see or call contacts

Configuration

Go to Client Permission > Contact Visibility

Add Rule

Click Add Rule and enter descriptive name

Apply To

Select users/groups

Select Phonebooks

Select which phonebooks to control

Set Permission Level

Choose: No Access, View Only, or Manage

Save

Click Save to apply

Result

Users see and access only permitted phonebooks with appropriate permissions.

Use Cases: Sales team manages customer contacts, all staff view company directory (read-only), managers see VIP contacts.


Default Permissions

Purpose

Set baseline permissions for all new users.

Go to Client Permission > Default Settings

Configure Menu Visibility

Configure standard menu visibility

Set Operations

Set default operation permissions

Define Visibility

Define default extension visibility

Set Contact Access

Set default contact access

Save as Default

Click Save as Default

Result

All new users automatically receive these baseline permissions.

Exception

Create specific rules to override defaults for certain users/groups.


Permission Priority

Rule Hierarchy

When multiple rules apply to a user:

  1. User-specific rules: Highest priority
  2. Group rules: Applied if user is member
  3. Default rules: Applied if no specific rules exist

Conflict Resolution: Most restrictive rule wins.

Example:

  • Default: All menus visible
  • Group rule (Sales): Hide Settings menu
  • User rule (John): Show Settings menu
  • Result: John sees Settings (user rule overrides group rule)

Testing Permissions

Create Test Account

Create test user account

Apply Rules

Apply permission rules to test account

Login and Verify

Login to Linkus as test user

Check Features

Verify menus and features match expectations

Adjust and Deploy

Adjust rules as needed, roll out to production users


Best Practices

Recommendations

  • Start Restrictive: Begin with limited permissions, add as needed
  • Group-Based: Use groups instead of individual user rules
  • Document Rules: Maintain documentation of permission structure
  • Regular Audits: Review permissions quarterly
  • User Feedback: Collect feedback on needed features
  • Compliance: Ensure permissions meet regulatory requirements

Common Permission Scenarios

Call Center Agents

  • Show: Dial Pad, Call History, Contacts (read-only)
  • Hide: Settings, Voicemail, Messaging
  • Operations: Disable call recording control, lock audio settings

Sales Team

  • Show: All menus
  • Operations: Enable all, including recording
  • Contacts: Full manage permissions for Sales phonebook

Reception

  • Show: Dial Pad, Contacts, Call History
  • Operations: Enable transfer, conference, park
  • Extension Visibility: See all extensions

Executives

  • Show: All menus
  • Operations: All enabled
  • Visibility: Hidden from general directory

Temporary/Contractors

  • Show: Dial Pad, Call History only
  • Operations: Minimal (no transfer, no recording)
  • Contacts: No access to company contacts

Configuration Steps

Go to Client Permission

Add Rule

Click Add Rule and enter Rule Name

Select Target

Select Target (users/groups)

Configure Menu Visibility

Configure Menu Visibility

Set Operation Permissions

Set Operation Permissions

Define Extension Visibility

Define Extension Visibility

Configure Contact Permissions

Configure Contact Permissions

Save

Click Save

Test

Test with target user account

Result

Permissions enforced immediately across all Linkus clients.


Next Steps