Famstack Users Guide

Controls whether you can change which team's projects you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their projects. This is useful for managers who oversee multiple teams or need cross-team visibility.

When Disabled: You can only see projects from teams you're directly assigned to. The team filter may be hidden or disabled, restricting you to your own team's projects only.

Use Case: Typically enabled for managers, administrators, and cross-functional roles. Disabled for individual contributors who should focus on their own team's work.

Restricts the project list to display only projects belonging to your currently selected team, even if you have access to multiple teams.

When Enabled: The project list automatically filters to show only projects from your current team. You won't see projects from other teams you have access to unless you explicitly switch teams (if team switching is enabled).

When Disabled: You can see projects from all teams you have access to in a single unified list, making it easier to view cross-team projects.

Use Case: Useful for organizations that want to maintain team boundaries and reduce information overload. Disabled when cross-team collaboration is encouraged.

Controls whether you can view and interact with projects that belong to teams other than your own.

When Enabled: You can open, view details, and potentially edit projects from other teams (depending on your other permissions). This enables cross-team collaboration and visibility.

When Disabled: You can only access projects from your own team. Attempting to access other teams' projects will result in an access denied message or the project won't appear in your views.

Use Case: Enabled for collaborative environments where teams need to see each other's work. Disabled for strict team isolation or when data confidentiality requires team boundaries.

Controls which teams appear in the team selection dropdown when creating a new project.

When Enabled: Only teams that are currently active appear in the dropdown. Inactive or archived teams are hidden, preventing assignment of projects to inactive teams.

When Disabled: All teams (both active and inactive) may appear in the dropdown, allowing assignment to any team.

Use Case: Typically enabled to prevent accidental assignment to inactive teams and maintain data integrity. Ensures projects are only created for active, functioning teams.

Controls whether you can select teams you're not assigned to when creating projects.

When Enabled: When creating a project, you can select any team from the dropdown, even if you're not a member of that team. This allows project managers to create projects for any team.

When Disabled: You can only select teams you're assigned to when creating projects, ensuring projects are created within your own team structure.

Use Case: Enabled for project managers and administrators who need to create projects across the organization. Disabled to maintain team boundaries and prevent cross-team project creation.

Controls whether you can modify a project's status (e.g., from Active to Completed, or from In Progress to On Hold).

When Enabled: You can change project status using status dropdowns or status change buttons. This allows you to track project progress and update project state as work progresses.

When Disabled: Project status is locked and cannot be changed. Only users with status change permission can update it. This prevents unauthorized status changes and maintains workflow integrity.

Use Case: Typically enabled for project managers and team leads who need to track project progress. May be disabled for team members to prevent accidental status changes.

Controls whether you can change a project's status to a previous state (e.g., moving from "Completed" back to "In Progress" or from "In Progress" back to "Planned").

When Enabled: You can move project status backwards in the workflow. This is useful when a project needs to be reopened, work needs to be redone, or status was changed incorrectly.

When Disabled: You can only move status forward (e.g., Planned → In Progress → Completed). Once a status is reached, you cannot go back, maintaining a forward-only workflow.

Use Case: Disabled for strict workflows where status progression should be one-way. Enabled when flexibility is needed to correct mistakes or handle project changes.

Defines which specific statuses you can change a project to, even if status changes are generally allowed.

How It Works: This creates a whitelist of statuses you can select. For example, you might be able to change status to "In Progress" or "On Hold" but not to "Completed" (which might require approval).

Example: A team member might be able to change status to "In Progress" or "Blocked" but cannot mark a project as "Completed" - only project managers can do that.

Use Case: Used to implement role-based status workflows where different roles can only move projects to certain statuses, ensuring proper approval processes and workflow control.

Controls whether you can see and view tasks (deliverables) that belong to projects from teams other than your own.

When Enabled: You can open projects from other teams and see all their tasks, task details, assignments, and progress. This enables cross-team visibility and collaboration.

When Disabled: Even if you can view a project from another team, you cannot see its tasks. Tasks are hidden to maintain team boundaries and task-level privacy.

Use Case: Enabled for collaborative environments or when teams need visibility into each other's work. Disabled when task-level information should remain team-private.

Controls whether you can add new tasks (deliverables) to projects that belong to other teams.

When Enabled: You can create tasks in projects from any team you have access to. This allows cross-team collaboration where team members can contribute tasks to other teams' projects.

When Disabled: You can only create tasks in projects from your own team. This maintains team boundaries and ensures tasks are created by the appropriate team members.

Use Case: Enabled for collaborative projects where multiple teams contribute. Disabled to maintain clear ownership and prevent unauthorized task creation in other teams' projects.

Controls whether you can see service line estimates (breakdown of estimated work by service type, such as Development, Design, Testing, etc.).

When Enabled: You can view detailed service line estimates showing how project work is broken down by service type, including estimated hours and costs per service line.

When Disabled: Service line estimates are hidden from view. You may still see overall project estimates but not the detailed breakdown by service type.

Use Case: Typically enabled for project managers and finance teams who need detailed cost breakdowns. May be disabled for team members who only need high-level project information.

Controls whether you can modify purchase order details that are linked to a project.

When Enabled: You can edit purchase order information directly from the project page, including PO number, dates, and related details. This allows project managers to update PO information as needed.

When Disabled: Purchase order information is read-only on projects. Changes must be made in the Purchase Order module itself, maintaining data integrity and preventing conflicts.

Use Case: Enabled when project managers need flexibility to update PO details. Disabled to maintain single source of truth and prevent data inconsistencies between projects and purchase orders.

Controls whether project start and end dates must fall within the date range specified in the linked purchase order.

When Enabled: When a project is linked to a purchase order, the project's start and end dates cannot extend beyond the PO's date range. This ensures billing accuracy and contract compliance. You'll see validation errors if you try to set dates outside the PO range.

When Disabled: Project dates can be set independently of purchase order dates, allowing flexibility in project planning even when linked to a PO.

Use Case: Enabled to ensure projects align with contract terms and billing periods. Prevents projects from being scheduled outside authorized work periods, maintaining financial accuracy and compliance.

Controls whether you can see the estimated hours for each service line in project estimates.

When Enabled: Estimated hours are displayed for each service line, showing how many hours are allocated to Development, Design, Testing, etc.

When Disabled: Estimated hours are hidden, even if service line estimates are visible. This may be used to hide detailed hour breakdowns while showing other estimate information.

Controls whether you can modify the estimated hours for service lines in project estimates.

When Enabled: You can adjust estimated hours for each service line, allowing you to refine estimates as project details become clearer.

When Disabled: Estimated hours are read-only. Changes must be made by users with edit permission, maintaining estimate integrity and preventing unauthorized modifications.

Controls whether you can see the estimated costs (monetary values) for each service line in project estimates.

When Enabled: Estimated costs are displayed showing the financial value allocated to each service line. This is important for budgeting and financial planning.

When Disabled: Cost information is hidden, even if other estimate details are visible. This may be used to restrict financial information to authorized personnel only.

Controls whether you can modify the estimated costs for service lines in project estimates.

When Enabled: You can adjust estimated costs, allowing you to update budget allocations and financial estimates as project scope changes.

When Disabled: Estimated costs are read-only. Only authorized users (typically finance or senior management) can modify cost estimates, maintaining financial control and budget integrity.

Controls whether checklists are available and can be used in projects.

When Enabled: Checklists feature is available. You can create, view, and manage checklists within projects to track completion of multiple items.

When Disabled: Checklists are not available. The checklist feature is hidden from project views, and you cannot create or use checklists.

Controls whether you can save new checklist items or changes to existing checklist items.

When Enabled: You can add new items to checklists and save changes. This allows you to build and maintain project checklists.

When Disabled: You cannot save checklist changes. You may be able to view checklists but cannot modify them, maintaining checklist integrity.

Controls whether you can check off individual checklist items as completed.

When Enabled: You can mark individual checklist items as done by checking them off. This allows you to track progress on checklist items.

When Disabled: You cannot mark items as complete. Checklist items remain unchecked, preventing progress tracking on individual items.

Controls whether you can mark an entire checklist as complete (all items done).

When Enabled: You can mark the entire checklist as complete, indicating all items are finished. This is useful for project milestones or phase completion.

When Disabled: You cannot mark checklists as complete. Checklists must be completed item-by-item, or completion must be done by authorized users.

Controls whether you can edit, delete, or reorder checklist items.

When Enabled: You can edit item descriptions, delete items, reorder items, and make other modifications to checklist structure.

When Disabled: Checklist items are read-only. You can view and check items but cannot modify their content or structure, maintaining checklist consistency.

Controls whether you can allocate hours at the individual resource (team member) level within projects, rather than just at the project or task level.

When Enabled: You can assign specific hour allocations to individual team members within a project. This allows detailed resource planning showing exactly how many hours each person is allocated to the project.

When Disabled: Hour allocation is done at higher levels (project or task level) only. You cannot specify individual team member hour allocations, simplifying resource planning.

Use Case: Enabled for detailed resource planning and capacity management. Allows project managers to see and plan individual team member workloads. Disabled when simpler, project-level allocation is sufficient.

Controls whether you can modify the estimated hours for tasks (deliverables).

When Enabled: You can update the estimated hours for tasks, allowing you to refine estimates as you learn more about the work required. This helps maintain accurate project planning.

When Disabled: Estimated hours are read-only. Only users with edit permission can modify task estimates, maintaining estimate integrity and preventing unauthorized changes.

Use Case: Typically enabled for project managers and team leads who need to adjust estimates. May be disabled for team members to prevent estimate inflation or unauthorized modifications.

Controls whether you can change which team's tasks you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their tasks. This is useful for managers who oversee multiple teams.

When Disabled: You can only see tasks from teams you're directly assigned to. The team filter may be hidden or disabled.

Controls which teams appear in the team selection dropdown when creating a new task.

When Enabled: Only teams that are currently active appear in the dropdown. Inactive or archived teams are hidden, preventing assignment of tasks to inactive teams.

When Disabled: All teams (both active and inactive) may appear in the dropdown.

Controls whether you can view and interact with tasks that belong to projects from teams other than your own.

When Enabled: You can access tasks in projects from other teams, enabling cross-team collaboration and visibility.

When Disabled: You can only access tasks from your own team's projects, maintaining team boundaries.

Controls whether you can modify a task's status (e.g., from Planned to In Progress, or from In Progress to Completed).

When Enabled: You can change task status using status dropdowns or drag-and-drop on the Task Board. This allows you to track task progress as work advances.

When Disabled: Task status is locked and cannot be changed. Only users with status change permission can update it.

Controls whether you can change a task's status to a previous state (e.g., moving from "Completed" back to "In Progress").

When Enabled: You can move task status backwards, useful when a task needs to be reopened or work needs to be redone.

When Disabled: You can only move status forward, maintaining a forward-only workflow.

Defines which specific statuses you can change a task to, even if status changes are generally allowed.

How It Works: Creates a whitelist of statuses you can select. For example, you might be able to change status to "In Progress" but not to "Completed" (which might require approval).

Controls whether you can modify the description, date, or other information on work items that have already been completed or submitted.

When Enabled: You can edit completed work items to correct mistakes, update descriptions, or change dates. This allows you to fix errors even after work items are marked as complete.

When Disabled: Completed work items are locked and cannot be edited. This prevents changes to historical time entries and maintains data integrity. Corrections may require administrator approval.

Use Case: Enabled when flexibility is needed to correct errors. Disabled to maintain audit trails and prevent tampering with historical time data.

Controls whether you can modify the number of hours logged on work items that have been completed.

When Enabled: You can adjust hours on completed work items, allowing you to correct time entry mistakes or update hours after completion.

When Disabled: Hours on completed work items are locked. This prevents changes to historical time data and maintains billing accuracy. Hour corrections may require manager approval.

Use Case: Typically disabled to prevent retroactive hour changes that could affect billing or reporting. Enabled only when necessary for error correction with proper oversight.

Controls whether you can modify estimated hours on work items that have been completed.

When Enabled: You can update estimated hours even after work is complete, allowing you to refine estimates based on actual work performed.

When Disabled: Estimated hours are locked once work items are completed, maintaining the original estimate for comparison purposes.

Controls whether you can see the estimated hours alongside actual hours logged in work items.

When Enabled: Estimated hours are displayed, allowing you to compare estimated vs actual time spent. This helps with planning and identifying estimation accuracy.

When Disabled: Estimated hours are hidden. You only see actual hours logged, not the original estimates.

Use Case: Enabled for project managers and team leads who need to track estimation accuracy. May be disabled for team members to reduce information overload.

Controls how long after creating a work item you can delete it. This creates a time window (e.g., until 10 AM the next day) during which work items can be deleted.

How It Works: After the specified time limit passes, work items become permanent and cannot be deleted. This prevents accidental deletion of important time entries while still allowing corrections shortly after entry.

Example: If set to "10 AM next day", you can delete a work item entered on Monday until 10 AM on Tuesday. After that, it's locked.

Use Case: Prevents deletion of historical time entries while allowing quick corrections for recent mistakes. Helps maintain accurate time records and billing data.

Controls how long after completing a work item you can still edit its hours. This creates a time window (e.g., until 10 AM the next day) during which hours can be modified.

How It Works: After the specified time limit passes, hours on completed work items become locked and cannot be changed. This prevents retroactive hour modifications while allowing corrections shortly after completion.

Example: If set to "10 AM next day", you can edit hours on a work item completed on Monday until 10 AM on Tuesday.

Use Case: Balances the need for error correction with the need to maintain historical data integrity. Prevents changes to old time entries that could affect billing or reporting.

Controls whether you can enter leave or holiday time entries for dates that haven't occurred yet.

When Enabled: You can log planned leave or holidays in advance. This allows you to pre-enter time off, helping with planning and ensuring your timesheet is complete.

When Disabled: You can only log leave/holiday for past or current dates. Future dates are not available for time entry, preventing premature leave logging.

Use Case: Enabled to allow advance planning of time off. Disabled to prevent logging leave before it's actually taken, maintaining accuracy of actual time off records.

Controls whether you can enter leave or holiday time entries for dates that have already passed.

When Enabled: You can log leave or holidays retroactively for past dates. This allows you to catch up on missed time entries or correct omissions.

When Disabled: You can only log leave/holiday for current or future dates. Past dates are locked, preventing retroactive leave entries.

Use Case: Enabled to allow correction of missed entries. Disabled to prevent backdating of leave, which could affect attendance records and payroll accuracy.

Controls whether you can create project work items for dates that are more than X working days in the past.

When Enabled: You cannot create project work items for dates that are more than X working days ago. This prevents logging time for dates that are too far in the past, helping maintain accurate and timely time tracking.

When Disabled: You can create project work items for any past date, allowing retroactive time entry without date restrictions.

Use Case: Enabled to encourage timely time entry and prevent backdating of work items. Helps maintain accurate project tracking and billing records. Typically set to 5-10 working days to allow for reasonable catch-up periods.

Controls whether you can create project work items for dates that are more than X working days in the future.

When Enabled: You cannot create project work items for dates that are more than X working days ahead. This prevents logging time too far in advance, ensuring time entries reflect actual work performed.

When Disabled: You can create project work items for any future date, allowing advance planning of time entries.

Use Case: Enabled to prevent premature time logging and ensure time entries reflect actual work. Typically set to 1-2 working days to allow for same-day or next-day planning while preventing excessive advance entries.

Controls whether you can assign project work items to dates that are more than X working days in the past.

When Enabled: You cannot assign work items to dates that are more than X working days ago. This prevents retroactive assignment of work items, maintaining assignment accuracy.

When Disabled: You can assign work items to any past date, allowing retroactive assignment.

Use Case: Similar to creation restrictions, this ensures work item assignments reflect actual work periods and prevents backdating of assignments.

Controls whether you can assign project work items to dates that are more than X working days in the future.

When Enabled: You cannot assign work items to dates that are more than X working days ahead. This prevents advance assignment of work items too far in the future.

When Disabled: You can assign work items to any future date, allowing long-term planning of assignments.

Use Case: Helps maintain realistic assignment planning and prevents assignments too far in advance that may not reflect actual work schedules.

Controls whether you can create non-project work items (administrative time, training, etc.) for dates that are more than X working days in the past.

When Enabled: You cannot create non-project work items for dates that are too far in the past, encouraging timely entry of administrative and other non-project time.

When Disabled: You can create non-project work items for any past date without restrictions.

Use Case: Similar to project work item restrictions, this ensures timely entry of all time types and maintains accurate records.

Controls whether you can create non-project work items for dates that are more than X working days in the future.

When Enabled: You cannot create non-project work items too far in advance, ensuring entries reflect actual time spent.

When Disabled: You can create non-project work items for any future date.

Controls whether you can assign non-project work items to dates that are more than X working days in the past.

When Enabled: Prevents retroactive assignment of non-project work items beyond the allowed time window.

When Disabled: Allows assignment to any past date.

Controls whether you can assign non-project work items to dates that are more than X working days in the future.

When Enabled: Prevents advance assignment of non-project work items too far in the future.

When Disabled: Allows assignment to any future date.

Controls whether you can create work items for dates that are Y working days in the past if you've already logged X hours for that date.

How It Works: This creates a combined restriction that considers both the date and hours already logged. For example, if set to "5 working days" and "8 hours", you cannot create additional work items for dates more than 5 days ago if you've already logged 8 hours for that date.

When Enabled: Prevents adding more work items to old dates that already have significant hours logged, reducing the likelihood of errors or duplicate entries.

When Disabled: You can create work items for any date regardless of hours already logged.

Use Case: Enabled to prevent retroactive changes to dates that already have substantial time logged, maintaining data integrity and preventing accidental over-logging.

Controls whether you can create work items that are immediately marked as completed, rather than starting in an "In Progress" or "Pending" status.

When Enabled: You can create work items and mark them as completed in one step. This is useful for quick entries of work that has already been finished.

When Disabled: New work items must be created in a non-completed status and then moved to completed separately. This enforces a workflow where work items progress through statuses.

Use Case: Enabled for quick time entry of completed work. Disabled to enforce status workflows and ensure proper tracking of work item progression.

Controls the maximum number of hours you can enter in a single work item entry.

How It Works: When creating or editing a work item, you cannot enter more than the specified maximum hours (e.g., 24 hours). This prevents unrealistic hour entries and helps catch data entry errors.

Example: If set to 24 hours, you cannot log more than 24 hours in a single work item, even if you worked longer. You would need to create multiple work items or split the time across multiple entries.

Use Case: Prevents data entry errors and unrealistic hour entries. Typically set to 24 hours to allow full-day entries while preventing mistakes like entering 240 hours instead of 24.

Controls whether you can only create work items for projects or tasks that match your assigned skills.

When Enabled: When creating work items, you can only select projects or tasks that require skills you have been assigned. Projects/tasks that don't match your skills are hidden from selection. This ensures work items are only created for work you're qualified to perform.

When Disabled: You can create work items for any project or task regardless of your skills. All available projects and tasks appear in selection dropdowns.

Use Case: Enabled to ensure proper skill matching and prevent assignment of work to unqualified team members. Helps maintain quality and ensures work is logged against appropriate projects. Disabled when skill matching is not required or when flexibility is needed.

Controls whether you can change which team's work items you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their work items. This is useful for managers who oversee multiple teams or need cross-team visibility.

When Disabled: You can only see work items from teams you're directly assigned to. The team filter may be hidden or disabled, restricting you to your own team's work items only.

Use Case: Typically enabled for managers, administrators, and cross-functional roles. Disabled for individual contributors who should focus on their own team's work.

Controls whether managers can view work items for employees other than themselves.

When Enabled: Managers can use an employee filter dropdown to view work items for any employee they manage or have access to. This enables managers to review and approve time entries for their team members.

When Disabled: You can only view your own work items, even if you're a manager. Employee filtering is not available.

Use Case: Enabled for managers and team leads who need to review and approve team members' time entries. Disabled for individual contributors who should only see their own work items.

Controls whether you can create work item entries on behalf of other employees.

When Enabled: You can create work items and assign them to other employees. This allows managers or administrators to log time for team members, which is useful when employees forget to log time or when bulk time entry is needed.

When Disabled: You can only create work items for yourself. All new work items are automatically assigned to you and cannot be reassigned to others.

Use Case: Enabled for managers and administrators who need to log time on behalf of team members. Disabled for individual contributors to ensure they log their own time and maintain accountability.

Controls which projects appear in the project selection dropdown when creating work items.

When Enabled: Only projects from your currently selected team appear in the project dropdown. Projects from other teams are hidden, even if you have access to them. This simplifies project selection and maintains team boundaries.

When Disabled: All projects you have access to appear in the dropdown, regardless of team. This allows you to log time against projects from multiple teams.

Use Case: Enabled to maintain team boundaries and simplify project selection. Disabled when cross-team project work is common and team members need to log time against projects from multiple teams.

Controls whether estimated hours are displayed alongside actual hours logged in work item views and lists.

When Enabled: Estimated hours are displayed next to actual hours, allowing you to compare estimated vs actual time spent. This helps track estimation accuracy and identify tasks that took longer or shorter than expected.

When Disabled: Only actual hours are displayed. Estimated hours are hidden, reducing information overload and focusing on actual time logged.

Use Case: Enabled for project managers and team leads who need to track estimation accuracy and project performance. Disabled for team members who only need to see actual hours logged without comparison data.

Controls which accounts appear in the account selection dropdown when logging non-billable work items.

When Enabled: All accounts in the system appear in the dropdown when logging non-billable time, not just accounts associated with your projects. This allows you to log administrative time, training, or other non-billable activities against any account.

When Disabled: Only accounts from your assigned projects appear in the dropdown. This restricts non-billable time logging to accounts you're already associated with.

Use Case: Enabled when non-billable time needs to be tracked against various accounts (e.g., internal projects, training accounts, administrative accounts). Disabled to maintain account boundaries and ensure non-billable time is only logged against relevant accounts.

Controls whether you can enter time in your timesheet.

When Enabled: You can access the timesheet interface and create new time entries. This is the fundamental permission required for logging work hours, leave, holidays, and other time-related activities.

When Disabled: You cannot access the timesheet entry interface. Time entry features are hidden or disabled, preventing you from logging any time. This may be used for employees who don't need to track time or during specific periods.

Use Case: Enabled for all employees who need to track their time. Disabled for employees who don't bill time or for specific roles that don't require time tracking.

Controls whether you can modify existing timesheet entries after they've been created.

When Enabled: You can edit timesheet entries to correct mistakes, update descriptions, change hours, or modify dates (subject to other date restrictions). This allows you to maintain accurate time records.

When Disabled: Timesheet entries are read-only once created. You cannot modify existing entries, requiring you to delete and recreate entries if corrections are needed (if deletion is allowed).

Use Case: Typically enabled to allow error correction. May be disabled for approved timesheets to maintain data integrity and prevent changes to submitted/approved time entries.

Controls whether you can approve timesheets submitted by other employees (typically managers and team leads).

When Enabled: You can view submitted timesheets from your team members and approve or reject them. Approved timesheets are typically locked from further editing and may be used for payroll or billing purposes.

When Disabled: You cannot approve timesheets, even if you're a manager. Timesheet approval features are hidden or disabled.

Use Case: Enabled for managers, team leads, and administrators who need to review and approve team members' time entries. Disabled for individual contributors who should only manage their own timesheets.

Controls whether you can enter leave or holiday time entries for dates that haven't occurred yet.

When Enabled: You can log planned leave or holidays in advance. This allows you to pre-enter time off, helping with planning and ensuring your timesheet is complete. Future dates are available for leave/holiday entry.

When Disabled: You can only log leave/holiday for past or current dates. Future dates are not available for time entry, preventing premature leave logging.

Use Case: Enabled to allow advance planning of time off and help employees prepare their timesheets. Disabled to prevent logging leave before it's actually taken, maintaining accuracy of actual time off records.

Controls whether you can enter leave or holiday time entries for dates that have already passed.

When Enabled: You can log leave or holidays retroactively for past dates. This allows you to catch up on missed time entries or correct omissions. Past dates are available for leave/holiday entry.

When Disabled: You can only log leave/holiday for current or future dates. Past dates are locked, preventing retroactive leave entries.

Use Case: Enabled to allow correction of missed entries and help employees catch up on timesheet entry. Disabled to prevent backdating of leave, which could affect attendance records and payroll accuracy.

Controls whether you can view and access timesheet pages for future dates that haven't occurred yet.

When Enabled: You can navigate to and view timesheet pages for future weeks or months. This allows you to see upcoming timesheet periods and plan ahead, even if you can't enter time for those dates yet.

When Disabled: Future timesheet pages are not accessible. You can only view current and past timesheets, preventing access to future periods.

Use Case: Enabled to allow planning and familiarization with upcoming timesheet periods. Disabled to restrict access to only relevant (current and past) timesheet periods.

Controls whether you can view and access timesheet pages for past dates.

When Enabled: You can navigate to and view timesheet pages for previous weeks or months. This allows you to review historical time entries and access past timesheet data.

When Disabled: Past timesheet pages are not accessible. You can only view current timesheets, preventing access to historical data.

Use Case: Typically enabled to allow review of historical time entries and access to past timesheet data. Disabled in rare cases where historical data access should be restricted.

Controls the maximum number of hours you can enter per day in your timesheet.

How It Works: When entering time for a specific date, you cannot log more than the specified maximum hours (e.g., 24 hours). This prevents unrealistic daily hour entries and helps catch data entry errors.

Example: If set to 24 hours, you cannot log more than 24 hours total for a single day across all work items, even if you worked longer. You would need to split the time across multiple days or contact an administrator.

Use Case: Prevents data entry errors and unrealistic daily hour entries. Typically set to 24 hours to allow full-day entries while preventing mistakes. May be set lower (e.g., 12 hours) for organizations with strict work-hour policies.

Controls how long into the current month you can still edit timesheet entries from the previous month.

How It Works: After X days into the current month, timesheet entries from the previous month become locked and cannot be edited. This creates a deadline for timesheet corrections and ensures timely closure of monthly timesheets.

Example: If set to 5 days, you can edit last month's timesheet entries until the 5th day of the current month. After that, last month's entries are locked and require administrator approval to modify.

Use Case: Ensures timesheets are finalized in a timely manner and prevents ongoing changes to historical data. Helps maintain accurate monthly records for payroll and billing. Typically set to 3-7 days to allow reasonable correction periods while ensuring timely closure.

Controls whether you can create work items for dates that are Y working days in the past if you've already logged X hours for that date.

How It Works: This creates a combined restriction that considers both the date and hours already logged. For example, if set to "5 working days" and "8 hours", you cannot create additional work items for dates more than 5 days ago if you've already logged 8 hours for that date.

When Enabled: Prevents adding more work items to old dates that already have significant hours logged, reducing the likelihood of errors or duplicate entries.

When Disabled: You can create work items for any date regardless of hours already logged.

Use Case: Enabled to prevent retroactive changes to dates that already have substantial time logged, maintaining data integrity and preventing accidental over-logging.

Controls whether you can change which team's timesheets you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their timesheets. This is useful for managers who oversee multiple teams or need cross-team visibility.

When Disabled: You can only see timesheets from teams you're directly assigned to. The team filter may be hidden or disabled, restricting you to your own team's timesheets only.

Use Case: Typically enabled for managers, administrators, and cross-functional roles. Disabled for individual contributors who should focus on their own team's timesheets.

Controls whether managers can view timesheets for employees other than themselves.

When Enabled: Managers can use an employee filter dropdown to view timesheets for any employee they manage or have access to. This enables managers to review and approve time entries for their team members.

When Disabled: You can only view your own timesheet, even if you're a manager. Employee filtering is not available.

Use Case: Enabled for managers and team leads who need to review and approve team members' timesheets. Disabled for individual contributors who should only see their own timesheet.

Controls whether you can only select projects that match your assigned skills when creating timesheet entries.

When Enabled: When creating timesheet entries, you can only select projects that require skills you have been assigned. Projects that don't match your skills are hidden from selection. This ensures timesheet entries are only created for work you're qualified to perform.

When Disabled: You can create timesheet entries for any project regardless of your skills. All available projects appear in selection dropdowns.

Use Case: Enabled to ensure proper skill matching and prevent assignment of work to unqualified team members. Helps maintain quality and ensures work is logged against appropriate projects. Disabled when skill matching is not required or when flexibility is needed.

Controls which projects appear in the project selection dropdown when creating timesheet entries.

When Enabled: Only projects from your currently selected team appear in the project dropdown. Projects from other teams are hidden, even if you have access to them. This simplifies project selection and maintains team boundaries.

When Disabled: All projects you have access to appear in the dropdown, regardless of team. This allows you to log time against projects from multiple teams.

Use Case: Enabled to maintain team boundaries and simplify project selection. Disabled when cross-team project work is common and team members need to log time against projects from multiple teams.

Controls which accounts appear in the account selection dropdown when logging non-billable timesheet entries.

When Enabled: All accounts in the system appear in the dropdown when logging non-billable time, not just accounts associated with your projects. This allows you to log administrative time, training, or other non-billable activities against any account.

When Disabled: Only accounts from your assigned projects appear in the dropdown. This restricts non-billable time logging to accounts you're already associated with.

Use Case: Enabled when non-billable time needs to be tracked against various accounts (e.g., internal projects, training accounts, administrative accounts). Disabled to maintain account boundaries and ensure non-billable time is only logged against relevant accounts.

Controls whether you can change which team's employees you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their employees. This is useful for managers who oversee multiple teams or HR administrators who need cross-team visibility.

When Disabled: You can only see employees from teams you're directly assigned to. The team filter may be hidden or disabled, restricting you to your own team's employees only.

Use Case: Typically enabled for managers, HR administrators, and cross-functional roles. Disabled for individual contributors who should only see their own team's employees.

Controls whether you can modify an employee's exit date or termination date in their profile.

When Enabled: You can set or update the exit/termination date for employees, marking when they left the organization. This is important for tracking employee lifecycle, maintaining accurate records, and ensuring proper access control (employees with exit dates may have restricted system access).

When Disabled: Exit/termination dates are read-only. Only users with this permission can update exit dates, maintaining data integrity and preventing unauthorized changes to employee status.

Use Case: Enabled for HR administrators and managers who need to track employee departures and update employee status. Disabled for regular users to prevent unauthorized changes to employee termination information.

Controls access to the standard/default report format, which provides a comprehensive overview of project and resource data.

When Enabled: You can generate and view the default report format, which typically includes key metrics, summaries, and standard data views.

When Disabled: The default report format is not available in your reports menu.

Controls access to a specific report format (Format 3) that may have a different layout or data presentation than the default format.

When Enabled: You can generate and view reports in Format 3, which may be customized for specific organizational needs or presentation requirements.

When Disabled: Format 3 reports are not available in your reports menu.

Controls access to reports showing how employees are being utilized across projects and activities.

When Enabled: You can generate reports showing employee utilization rates, helping identify overallocation, underutilization, and resource capacity. This is essential for resource planning and workload management.

When Disabled: Employee utilization reports are not available, restricting visibility into resource allocation and capacity.

Use Case: Enabled for managers, resource planners, and administrators who need to track and optimize resource utilization. Disabled for individual contributors who don't need utilization insights.

Controls access to reports showing your own personal utilization rate and how your time is allocated.

When Enabled: You can generate reports showing your personal utilization, helping you understand how your time is distributed across projects, tasks, and activities. This is useful for self-assessment and workload planning.

When Disabled: Personal utilization reports are not available, preventing you from viewing your own utilization metrics.

Use Case: Typically enabled for all employees to allow self-monitoring of workload and time allocation. Disabled when personal utilization tracking is not needed or should be restricted.

Controls access to reports showing your own timesheet entries and time tracking data.

When Enabled: You can generate reports showing your timesheet entries, hours logged, project assignments, and time tracking history. This helps you review your time entries and track your work history.

When Disabled: Personal timesheet data reports are not available, preventing you from generating reports of your own time entries.

Use Case: Typically enabled for all employees to allow review of their own time tracking data. Useful for verifying timesheet accuracy and tracking work history.

Controls access to detailed, raw data exports of your timesheet information.

When Enabled: You can generate comprehensive data dump reports of your timesheet entries, typically in formats suitable for analysis or import into other systems. These reports contain detailed, unformatted data.

When Disabled: Data dump reports of your timesheet data are not available.

Use Case: Enabled when employees need detailed data exports for personal records, analysis, or integration with other tools. Disabled when detailed data exports are not needed or should be restricted.

Controls access to reports showing activity and usage across the system or site.

When Enabled: You can generate reports showing system-wide activity, user actions, feature usage, and other site-level metrics. This provides insights into system usage and engagement.

When Disabled: Site activity reports are not available, restricting visibility into system-wide activity.

Use Case: Enabled for administrators and system managers who need to monitor system usage and activity. Disabled for regular users who don't need system-level insights.

Controls access to reports showing project information organized by required skills or skill categories.

When Enabled: You can generate reports that break down projects by the skills they require, helping identify skill gaps, resource needs, and project-skill matching. This is useful for resource planning and skill-based project assignment.

When Disabled: Skill-based project reports are not available.

Use Case: Enabled for resource managers and project planners who need to match projects with skilled resources. Disabled when skill-based reporting is not needed.

Controls access to a specific report format (commonly referred to as the "15% report") that may track a particular metric or compliance requirement.

When Enabled: You can generate the 15% report, which may track specific project metrics, compliance measures, or organizational KPIs.

When Disabled: The 15% report is not available in your reports menu.

Use Case: Enabled for users who need access to this specific report format, typically for compliance or specific organizational reporting requirements.

Controls access to reports comparing estimated vs actual work, organized by deliverables/tasks and sorted by task date.

When Enabled: You can generate reports showing how actual work compared to estimates, broken down by deliverables and organized by task dates. This helps identify estimation accuracy and track project performance over time.

When Disabled: Estimate vs actual reports organized by task date are not available.

Use Case: Enabled for project managers and analysts who need to track estimation accuracy and project performance. Essential for improving future estimates and identifying trends.

Controls access to reports comparing estimated vs actual work, organized by deliverables/tasks and sorted by activity date (when work was performed).

When Enabled: You can generate reports showing how actual work compared to estimates, broken down by deliverables and organized by when activities occurred. This provides a different view than task date reports, focusing on when work was actually performed.

When Disabled: Estimate vs actual reports organized by activity date are not available.

Use Case: Enabled for project managers who need to analyze work patterns and compare estimates to actuals based on when work was performed, rather than when tasks were scheduled.

Controls access to reports showing employee utilization broken down by week within a monthly period.

When Enabled: You can generate reports showing how employee utilization varies week by week within a month, helping identify weekly patterns, workload fluctuations, and capacity trends.

When Disabled: Week-wise monthly utilization reports are not available.

Use Case: Enabled for resource managers and planners who need detailed weekly utilization insights to manage capacity and identify workload patterns.

Controls access to comprehensive end-to-end reports showing employee utilization by week across monthly periods.

When Enabled: You can generate detailed end-to-end reports showing complete weekly utilization data across monthly periods, providing comprehensive visibility into resource utilization patterns.

When Disabled: End-to-end week-wise monthly utilization reports are not available.

Use Case: Enabled for advanced resource planning and analysis, providing comprehensive utilization insights across time periods.

Controls access to reports showing purchase order estimates broken down by week.

When Enabled: You can generate reports showing purchase order estimates organized by week, helping track PO-related work and costs over time.

When Disabled: Weekly PO estimation reports are not available.

Use Case: Enabled for project managers and finance teams who need to track purchase order estimates and related work on a weekly basis.

Controls access to reports showing project hours logged, organized by week.

When Enabled: You can generate reports showing how many hours were logged on projects each week, helping track project progress, resource allocation, and workload distribution over time.

When Disabled: Weekly project hours reports are not available.

Use Case: Enabled for project managers and team leads who need to track weekly project progress and hours logged. Useful for monitoring project velocity and resource allocation.

Controls access to reports showing employee utilization broken down by the skills they're using.

When Enabled: You can generate reports showing how employees are utilized across different skill categories, helping identify skill usage patterns, skill-based capacity, and resource allocation by expertise area.

When Disabled: Skill-based utilization reports are not available.

Use Case: Enabled for resource managers and planners who need to understand how skills are being utilized and ensure proper skill-based resource allocation.

Controls access to reports showing employee utilization broken down by project categories.

When Enabled: You can generate reports showing how employees are utilized across different project categories, helping understand resource allocation by project type, client type, or other categorization schemes.

When Disabled: Category-based utilization reports are not available.

Use Case: Enabled for managers and analysts who need to understand resource allocation across different project categories and make strategic resource planning decisions.

Controls access to comprehensive, raw data export reports containing detailed system data.

When Enabled: You can generate data dump reports containing detailed, unformatted data exports suitable for analysis, import into other systems, or comprehensive data review. These reports typically contain extensive data in formats like CSV or Excel.

When Disabled: Data dump reports are not available, restricting access to detailed data exports.

Use Case: Enabled for administrators, analysts, and users who need comprehensive data exports for analysis, reporting, or system integration. Disabled when detailed data exports should be restricted.

Controls access to reports showing how resources (employees) are allocated across projects and activities.

When Enabled: You can generate reports showing resource allocation, helping identify who is assigned to which projects, allocation percentages, and resource distribution. This is essential for resource planning and capacity management.

When Disabled: Resource allocation reports are not available, restricting visibility into how resources are assigned and allocated.

Use Case: Enabled for resource managers, project managers, and administrators who need to track and manage resource allocation. Disabled for individual contributors who don't need allocation visibility.

Controls access to reports showing project completion status, progress, and completion metrics.

When Enabled: You can generate reports showing which projects are completed, completion percentages, completion dates, and related completion metrics. This helps track project status and identify completed work.

When Disabled: Project completion reports are not available.

Use Case: Enabled for project managers, executives, and stakeholders who need to track project completion and status. Useful for portfolio management and project status reporting.

Controls whether you can create, save, and manage custom report configurations and settings.

When Enabled: You can create and save custom report configurations with specific filters, date ranges, team selections, and other parameters. Saved configurations can be reused, making it easier to generate frequently needed reports without re-entering parameters each time.

When Disabled: You cannot save report configurations. You can still generate reports but must enter parameters each time, and cannot reuse saved configurations.

Use Case: Enabled for users who frequently generate reports with specific parameters and want to save time by reusing configurations. Disabled when report configuration management should be restricted.

Controls whether you can change which team's data you're including in reports using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and include their data in reports. This is useful for managers who oversee multiple teams or need cross-team reporting.

When Disabled: Reports can only include data from teams you're directly assigned to. The team filter may be hidden or disabled, restricting reports to your own team's data only.

Use Case: Typically enabled for managers, administrators, and cross-functional roles. Disabled for individual contributors who should only generate reports for their own team.

Controls whether you can view and access scheduled reports (automated reports sent on a schedule) from all teams, not just your own.

When Enabled: You can view and access scheduled reports from all teams in the organization, providing cross-team visibility into automated reporting.

When Disabled: You can only access scheduled reports from your own team. Scheduled reports from other teams are not visible or accessible.

Use Case: Enabled for administrators and managers who need organization-wide visibility into scheduled reports. Disabled to maintain team boundaries and restrict access to team-specific scheduled reports.

Controls whether you can view and interact with purchase orders that belong to teams other than your own.

When Enabled: You can open, view details, and potentially edit purchase orders from other teams (depending on your other permissions). This enables cross-team collaboration and visibility into purchase orders across the organization.

When Disabled: You can only access purchase orders from your own team. Attempting to access other teams' purchase orders will result in an access denied message or the PO won't appear in your views.

Use Case: Enabled for collaborative environments where teams need to see each other's purchase orders. Disabled for strict team isolation or when purchase order confidentiality requires team boundaries.

Controls which projects appear in the project selection dropdown when creating a new purchase order.

When Enabled: All projects in the system appear in the dropdown when creating a purchase order, regardless of team. This allows you to link purchase orders to any project.

When Disabled: Only projects from your team appear in the dropdown, restricting purchase order creation to projects within your team.

Use Case: Enabled when purchase orders need to be linked to projects across teams. Disabled to maintain team boundaries and ensure purchase orders are only created for team-specific projects.

Controls whether you can create new client or customer accounts in the system.

When Enabled: You can create new accounts, setting up client information, contact details, and account settings. This is essential for sales and account management teams.

When Disabled: You cannot create new accounts. Account creation features are hidden or disabled.

Controls whether you can modify existing account information.

When Enabled: You can update account details, contact information, settings, and other account fields.

When Disabled: Accounts are read-only. You cannot modify account information.

Controls whether you can mark accounts as deleted.

When Enabled: You can delete accounts, which typically hides them from normal views but retains data for recovery purposes.

When Disabled: You cannot delete accounts. Account deletion is not available.

Controls whether you can permanently delete accounts from the system.

When Enabled: You can permanently remove accounts, which cannot be undone and removes all account data.

When Disabled: Permanent account removal is not available. Accounts can only be deleted (soft delete), not permanently removed.

Controls whether accounts from all teams appear in account lists and dropdowns.

When Enabled: Accounts from all teams are visible, allowing you to see and select accounts across the organization.

When Disabled: Only accounts from your team are visible, maintaining team boundaries for account access.

Controls whether team filtering is applied when viewing accounts.

When Enabled: All accounts are shown without team filtering, providing organization-wide account visibility.

When Disabled: Accounts are filtered by team, showing only accounts relevant to your team assignments.

Controls whether you can create new invoices in the system.

When Enabled: You can create invoices, linking them to projects, purchase orders, or accounts, and setting up billing details.

When Disabled: You cannot create invoices. Invoice creation features are hidden or disabled.

Controls whether you can modify existing invoice information.

When Enabled: You can update invoice details, amounts, dates, and other invoice fields.

When Disabled: Invoices are read-only. You cannot modify invoice information once created.

Controls whether you can remove invoices from the system.

When Enabled: You can remove invoices, which may delete them permanently or mark them as removed depending on system configuration.

When Disabled: You cannot remove invoices. Invoice removal is not available.

Controls whether you can view invoice information and details.

When Enabled: You can access and view invoice details, amounts, dates, and related information.

When Disabled: Invoices are not visible. You cannot access invoice information.

Controls whether you can create new attendance entries or records.

When Enabled: You can create attendance records, logging employee attendance, check-in/check-out times, and attendance-related information.

When Disabled: You cannot create attendance records. Attendance creation features are hidden or disabled.

Controls whether you can delete attendance entries.

When Enabled: You can remove attendance records, allowing correction of attendance data.

When Disabled: You cannot delete attendance records. Attendance data is permanent once created.

Controls whether you can view attendance information and records.

When Enabled: You can access and view attendance data, including check-in/check-out times, attendance history, and related information.

When Disabled: Attendance information is not visible. You cannot access attendance data.

Controls whether you can change which team's attendance data you're viewing using the team filter dropdown.

When Enabled: You can use the team dropdown filter to switch between different teams and view their attendance data. This is useful for managers who oversee multiple teams.

When Disabled: You can only see attendance from teams you're directly assigned to. The team filter may be hidden or disabled.

Controls whether you can create new holiday entries in the system calendar.

When Enabled: You can create holidays, setting up company-wide or team-specific holidays, dates, and holiday information.

When Disabled: You cannot create holidays. Holiday creation features are hidden or disabled.

Controls whether you can modify existing holiday information.

When Enabled: You can update holiday dates, names, descriptions, and other holiday fields.

When Disabled: Holidays are read-only. You cannot modify holiday information once created.

Controls whether you can remove holidays from the system calendar.

When Enabled: You can remove holidays, deleting them from the calendar.

When Disabled: You cannot remove holidays. Holiday removal is not available.

Controls whether you can create and use multiple task boards (Kanban boards) for different views or purposes.

When Enabled: You can create multiple task boards, each with its own configuration, columns, and task filtering. This allows you to organize tasks in different ways (e.g., by project, by team, by priority).

When Disabled: Only a single default task board is available. You cannot create additional task boards.

Use Case: Enabled when teams need multiple board views for different purposes or projects. Disabled to simplify the interface when a single board view is sufficient.

Controls whether you can view and access task boards from all teams, not just your own.

When Enabled: You can access task boards from all teams in the organization, providing cross-team visibility into task management and workflows.

When Disabled: You can only access task boards from your own team. Other teams' boards are not visible or accessible.

Use Case: Enabled for managers and administrators who need organization-wide visibility. Disabled to maintain team boundaries and restrict board access to team members only.

Controls whether you can create new tasks directly from the task board interface.

When Enabled: You can add new tasks directly on the task board, typically by clicking an "Add Task" button or similar action. This provides quick task creation without navigating away from the board.

When Disabled: You cannot create tasks from the board. Tasks must be created through other interfaces (e.g., project details page).

Controls whether you can modify task information directly from the task board interface.

When Enabled: You can edit task details, names, descriptions, assignments, and other fields directly from the board view, typically by clicking on tasks or using inline editing.

When Disabled: Tasks on the board are read-only. You must navigate to the task details page to make edits.

Controls whether you can delete tasks directly from the task board.

When Enabled: You can delete tasks from the board interface, typically through a delete action or button on task cards.

When Disabled: You cannot delete tasks from the board. Task deletion must be done through other interfaces.

Controls whether you can permanently remove tasks directly from the task board.

When Enabled: You can permanently remove tasks from the board, which cannot be undone.

When Disabled: Permanent task removal is not available from the board interface.

Controls whether you can modify task board settings, columns, filters, and other board configuration options.

When Enabled: You can customize board columns, status columns, filters, grouping options, and other board settings to match your workflow preferences.

When Disabled: Board configuration is read-only. You cannot modify board settings or layout.

Use Case: Enabled for board owners and administrators who need to customize board layouts. Disabled when board configuration should be standardized across the organization.

Controls whether you can delete work items (time entries) directly from the task board interface.

When Enabled: You can delete work items associated with tasks directly from the board view.

When Disabled: Work item deletion is not available from the board. Work items must be deleted through other interfaces.

Controls whether you can permanently remove work items directly from the task board.

When Enabled: You can permanently remove work items from the board, which cannot be undone.

When Disabled: Permanent work item removal is not available from the board interface.

Controls whether you can view existing feedback templates.

When Enabled: You can see and browse available feedback templates, viewing their structure, questions, and configuration.

When Disabled: Feedback templates are not visible. You cannot access template information.

Controls whether you can create new feedback templates.

When Enabled: You can create new templates, defining questions, structure, and configuration for feedback collection.

When Disabled: You cannot create new templates. Template creation is restricted.

Controls whether you can modify existing feedback template structure and questions.

When Enabled: You can update template questions, structure, and configuration.

When Disabled: Templates are read-only. You cannot modify template content.

Controls whether you can create copies of existing feedback templates.

When Enabled: You can duplicate templates, creating new templates based on existing ones. This is useful for creating variations of templates or reusing template structures.

When Disabled: Template duplication is not available.

Controls whether you can delete feedback templates from the system.

When Enabled: You can remove templates, deleting them from the template library.

When Disabled: Template removal is not available. Templates cannot be deleted.

Controls whether you can view feedback requests that have been sent or received.

When Enabled: You can see feedback requests, including requests sent to you, requests you've sent, and overall request status.

When Disabled: Feedback requests are not visible. You cannot access request information.

Controls whether you can create and send new feedback requests to others.

When Enabled: You can create feedback requests, select recipients, choose templates, and send requests for feedback.

When Disabled: You cannot create or send feedback requests. Request creation is restricted.

Controls whether you can modify feedback requests after they've been created.

When Enabled: You can update request details, recipients, or other request information before activation.

When Disabled: Requests are read-only once created. You cannot modify request details.

Controls whether you can activate feedback requests, making them active and sending them to recipients.

When Enabled: You can activate feedback requests, which typically sends notifications to recipients and makes the request available for response.

When Disabled: You cannot activate requests. Request activation is restricted to authorized users.

Controls whether you can delete feedback requests from the system.

When Enabled: You can remove feedback requests, deleting them and canceling any pending requests.

When Disabled: Request removal is not available. Requests cannot be deleted.

Controls whether you can change the status of feedback requests (e.g., from Pending to Completed, or from Active to Closed).

When Enabled: You can update request status, tracking the progress and lifecycle of feedback requests.

When Disabled: Request status is read-only. You cannot change request status.

Controls whether you can resend feedback requests to recipients, typically to remind them or send to additional recipients.

When Enabled: You can resend requests, which may send reminder notifications or extend the request to additional recipients.

When Disabled: Request resending is not available. Requests can only be sent once.

Controls whether you can view available checklist templates or saved checklists.

When Enabled: You can see and browse checklists, viewing their items and structure.

When Disabled: Checklists are not visible. You cannot access checklist information.

Controls whether you can create new checklist templates or saved checklists.

When Enabled: You can create new checklists, defining items and structure for reuse across projects or tasks.

When Disabled: You cannot create new checklists. Checklist creation is restricted.

Controls whether you can modify existing checklist items and structure.

When Enabled: You can update checklist items, add or remove items, and modify checklist structure.

When Disabled: Checklists are read-only. You cannot modify checklist content.

Controls whether you can create copies of existing checklists.

When Enabled: You can duplicate checklists, creating new checklists based on existing ones. This is useful for creating variations or reusing checklist structures.

When Disabled: Checklist duplication is not available.

Controls whether you can delete checklists from the system.

When Enabled: You can remove checklists, deleting them from the checklist library.

When Disabled: Checklist removal is not available. Checklists cannot be deleted.

Controls whether you can create new teams in the organization.

When Enabled: You can create new teams, setting up team names, members, and team configuration. This is essential for organizational structure management.

When Disabled: You cannot create new teams. Team creation is restricted to administrators.

Use Case: Enabled for HR administrators and organizational managers who need to set up team structures. Disabled for regular users to maintain organizational structure integrity.

Controls whether you can mark teams as deleted.

When Enabled: You can delete teams, which typically hides them from normal views but retains team data and member associations for recovery purposes.

When Disabled: You cannot delete teams. Team deletion is restricted.

Controls whether you can permanently delete teams from the system.

When Enabled: You can permanently remove teams, which cannot be undone and may remove team associations and data.

When Disabled: Permanent team removal is not available. Teams can only be deleted (soft delete), not permanently removed.

Use Case: Typically restricted to system administrators only, as permanent team removal can have significant organizational impact.

Controls whether you can register devices (such as mobile devices or computers) for system access or authentication.

When Enabled: You can register devices, which may be used for two-factor authentication, device-based access control, or device management.

When Disabled: Device registration is not available. You cannot register new devices.

Use Case: Enabled when device-based authentication or access control is used. Disabled when device registration should be managed by administrators only.

Controls whether you can access the scheduler or calendar view interface.

When Enabled: You can access scheduler views, which may show resource schedules, project timelines, or calendar-based planning interfaces.

When Disabled: Scheduler views are not accessible. Scheduler features are hidden or disabled.

Use Case: Enabled for users who need calendar or scheduling functionality. Disabled when scheduler views are not needed or should be restricted.

Controls whether you can view system service health, status, and monitoring information.

When Enabled: You can access service health dashboards, status pages, and system monitoring information, helping you understand system availability and performance.

When Disabled: Service health information is not visible. System status and health monitoring are restricted.

Use Case: Typically enabled for administrators and technical users who need to monitor system health. Disabled for regular users who don't need system-level information.

Controls whether you can access and modify company-wide settings and configuration.

When Enabled: You can access company settings pages, where you can configure organization-wide options, preferences, and system settings.

When Disabled: Company settings are not accessible. Company configuration is restricted to administrators.

Use Case: Typically restricted to administrators and authorized users only, as company settings affect the entire organization.

Controls whether you can modify localization settings such as language, date format, timezone, and regional preferences.

When Enabled: You can change your personal localization settings, customizing how dates, times, numbers, and text are displayed based on your regional preferences.

When Disabled: Localization settings are read-only or managed centrally. You cannot change personal localization preferences.

Use Case: Typically enabled for all users to allow personalization of display formats. Disabled when localization should be standardized across the organization.

Controls whether you can access and modify notification settings and preferences.

When Enabled: You can configure notification preferences, choosing which types of notifications you receive, notification channels (email, in-app, etc.), and notification frequency.

When Disabled: Notification settings are not accessible. Notification preferences are managed centrally or cannot be customized.

Use Case: Typically enabled for all users to allow personalization of notification preferences. Disabled when notification settings should be standardized or managed centrally.