Understanding Roles & Permissions
Comprehensive guide to the role-based access control system
Overview
Syndik uses a comprehensive role-based access control (RBAC) system that allows you to precisely control what each user can see and do within the platform. This ensures data security while maintaining operational efficiency.
Security First
Always follow the principle of least privilege - grant users only the minimum access they need to perform their job functions.
Role Hierarchy
Syndik follows a hierarchical permission structure where higher-level roles inherit permissions from lower-level roles:
Complete system control with access to all features and settings.
Full property management with limited system administration.
Day-to-day property operations and resident services.
Specialized access for specific job functions.
Permission Types
Syndik uses granular permissions that can be assigned individually or as part of role packages:
- • View properties and units
- • Access resident information
- • Read financial reports
- • View maintenance requests
- • Access communication logs
- • Update property information
- • Modify resident records
- • Process payments
- • Manage work orders
- • Send communications
- • Create/delete records
- • Manage user accounts
- • Configure system settings
- • Access sensitive data
- • Export bulk data
- • Audit log access
- • Security settings
- • Permission management
- • Integration controls
- • Data retention policies
Creating Custom Roles
You can create custom roles tailored to your organization's specific needs:
Navigate to Role Management
Settings → Users & Permissions → Role Management
Create New Role
Click "Add Custom Role" and enter role name and description
Select Permissions
Choose individual permissions or start from an existing role template
Test and Deploy
Test the role with a test user before assigning to production users
Security Best Practices
- ✓ Follow principle of least privilege
- ✓ Regularly review user permissions
- ✓ Use role templates for consistency
- ✓ Document custom role purposes
- ✓ Test roles before deployment
- ✓ Remove access immediately when staff leave
- ✗ Don't share admin credentials
- ✗ Don't give excessive permissions
- ✗ Don't create roles without documentation
- ✗ Don't ignore permission audit alerts
- ✗ Don't use generic role names
- ✗ Don't bypass the approval process
Common Examples
Here are some common role configurations for different scenarios:
Allowed Actions:
- • View available units
- • Schedule tours
- • Create prospect records
- • Process applications
- • Generate lease documents
Restricted Access:
- • Financial reporting
- • Maintenance management
- • User administration
- • Property settings
- • Bulk data export
Allowed Actions:
- • Manage work orders
- • Assign maintenance staff
- • Track inventory
- • Communicate with residents
- • Generate maintenance reports
Restricted Access:
- • Lease management
- • Financial data
- • User permissions
- • Property configuration
- • Legal documents
If you need immediate assistance, please contact our support team.
Support Hours: Monday - Friday, 9 AM - 6 PM
Please sign in to rate this article