Within Workslayr, roles define an employee’s access rights and capabilities across the platform. Understanding what roles are in Workslayr is crucial for managing your team effectively and ensuring every user has the appropriate level of access to perform their tasks without unnecessary privileges.
Understanding Workslayr Roles #
Workslayr’s flexible roles system allows you to precisely control who can view, create, edit, or delete information within different modules. Essentially, a role is a collection of permissions that dictate what actions a user can take. This granular control is vital for maintaining data security and streamlining your operational workflows.
For instance, an employee in a “Project Manager” role might have the ability to create and manage projects, assign employees to tasks, and view time logs for their team. Conversely, an employee in a “Team Member” role might only be able to view their assigned projects and submit their own clock in/out times. This structure ensures that users are only exposed to the functions and data relevant to their responsibilities, enhancing efficiency and reducing potential errors.
Default and Custom Role Management #
Workslayr comes equipped with Default Roles that provide common sets of permissions for various functions within a service-based business. These pre-configured roles serve as an excellent starting point for new accounts. However, recognizing that every business has unique needs, Workslayr also offers the ability to create Custom Roles. This allows you to tailor roles precisely to your organizational structure and specific operational requirements.
When defining a Custom Role, you set individual permission types for each module. For example, you can grant “view” permissions for invoices to one role, while another role might have the ability to both view and edit invoices. This granular control also extends to areas like client management, products & services, and expenses, ensuring sensitive information is only accessible to authorized personnel.
Workslayr supports a clear role hierarchy, where permissions can be inherited or specifically overridden. In situations where an employee requires temporary or unique access that deviates from their assigned role, Employee Permission Overrides can be applied. This is particularly useful when to use overrides for specific scenarios without altering the entire role’s definition or creating a brand new custom role.
Workslayr utilizes a robust system of roles and permissions to manage user access and define responsibilities within your organization. Understanding the default roles is crucial for effectively setting up your team and ensuring proper operational flow. These pre-configured roles provide a solid foundation for managing access to various Workslayr modules and functionalities.
Understanding Default Roles #
Workslayr comes with essential default roles designed to cater to the fundamental administrative and employee functions within a service-based business. These roles help streamline operations by granting appropriate access levels to different users. While these roles are immediately available, you also have the flexibility to customize them or create custom roles to precisely fit your business needs.
The primary purpose of what a role is in Workslayr is to define a set of permissions that dictate what a user can view, edit, create, or delete within the platform. This structured approach helps maintain data integrity and operational efficiency.
Key Default Roles #
Workslayr offers two core default roles that form the backbone of your team’s access structure:
- Administrator Role: Users assigned this role typically have comprehensive access across the entire Workslayr platform. This includes managing employees, overseeing all projects, handling client management, configuring pipelines and stages for deals, and managing various settings. They can view, edit, and delete most data, and administer system-wide configurations. This role is essential for company owners or top-level managers who require a complete overview and control of operations, as seen on the Admin Dashboard.
- Employee Role: This role is designed for individual team members and provides access to features directly relevant to their daily tasks. Employees can typically manage their own My Dashboard, clock in and out, log time against projects and tasks, view assigned invoices or estimates, and submit expenses for approval. Their access to client and project details is generally limited to what they are directly involved with, focusing on execution rather than administration.
The distinction between these roles is evident in the My Dashboard vs Admin Dashboard functionalities. An Administrator can access all company-wide data and analytics, whereas employees see information tailored to their individual performance and assignments.
Role Hierarchy and Permissions #
Workslayr’s role hierarchy ensures that higher-level roles naturally encompass broader permissions, while lower-level roles have more restricted access. Permission inheritance means that if a permission is granted at a higher level (e.g., to an admin), it doesn’t necessarily need to be explicitly granted to an employee unless there’s a specific override. You can fine-tune these permissions using employee permission overrides to grant or restrict specific access for individual users beyond their assigned role.
For instance, while a default employee might not be able to create proposals or send invoices, an administrator could grant specific employees these capabilities if their job requires it. This flexibility allows businesses to maintain a secure and efficient operational environment while adapting to specific team structures and responsibilities.
Workslayr allows the creation of custom roles to define specific access levels and permissions for employees. This enables granular control over what information employees can view, create, edit, or delete within the platform. Custom roles supplement the default roles provided by Workslayr.
How to Create a Custom Role #
To create a custom role, navigate to the Roles section in your settings. This process involves naming the role and then assigning specific permissions for each module within Workslayr.
- Access the Roles management interface.
- Select the option to create a new role.
- Provide a Role Name for identification.
- Configure permission types (View, Create, Edit, Delete) for various modules such as Projects, Invoices, Employees, Clients, and Expenses.
- Save the new custom role configuration.
Custom Role Application #
Once created, custom roles can be assigned to individual employees. When assigning a role, the employee inherits the permissions defined within that role. Individual employee permission overrides can be applied subsequently if specific adjustments are necessary, which take priority over the assigned role’s permissions.
Understanding the role hierarchy helps in structuring custom roles effectively. Custom roles streamline management by allowing you to standardize access for groups of users rather than configuring permissions for each user individually.
Workslayr utilizes a role hierarchy to structure user access and permissions. This system determines what actions a user can perform and which data they can view within the platform. Roles ensure users have appropriate access levels for their responsibilities.
Permissions are defined within each role and dictate specific capabilities. For example, a role might allow a user to view projects but not edit them. The hierarchy is primarily managed through Permission Types, which include options like View, Edit, or Delete.
How Role Hierarchy Functions #
Each user account is assigned a specific role. This role contains a set of predefined permissions. When a user logs in, Workslayr checks their assigned role to determine their functionalities across modules such as Employees, Clients, and Deals & Pipelines, as well as features including Invoices and Expenses.
Workslayr provides Default Roles with common permission sets. Administrators can also create Custom Roles to tailor access levels to specific organizational needs.
- Permission Inheritance: Permissions assigned to a role apply to all users holding that role.
- Override Capability: Individual user permissions can be adjusted using Employee Permission Overrides. This allows for granular control, enabling specific users to have different access than their assigned role.
- Module Specificity: Permissions are typically configured per module or feature, ensuring precise control over data access and operational functions.
Understanding the What Roles Are in Workslayr is crucial for managing user access effectively.
