Users Support Records

Retrieval metadata

feature_group: "Users"
record_count: 2
approx_page_tokens: 1416
recommended_chunking: one Knowledge Record section per vector chunk

Feature group overview

This page contains chatbot training records for Users sub-features. Retrieve one ### Knowledge Record: chunk at a time when possible.

This section contains chatbot training records for Users sub-features.

Knowledge Record: Users / Users, users are visible in a table view (First Name, Last Name, Email, Permi...

record_id: LFS-users-users-users-are-visible-in-a-table-view-first-name-last-name-email-permi

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting
• permissions_visibility

Sample user utterances

• How do I set up Users, users are visible in a table view (First Name, Last Name, Email, Permi in Lexul?
• When should we use Users, users are visible in a table view (First Name, Last Name, Email, Permi?
• Why is Users, users are visible in a table view (First Name, Last Name, Email, Permi not working or not showing?
• Can Lexul handle Users, users are visible in a table view (First Name, Last Name, Email, Permi for our workflow?

Entities to extract

• user_role
• workspace
• feature_area
• technician_name
• foreman_name
• crew_name
• time_type

Approved answer basis

User records control login, role permissions, activity, schedule, assigned work orders, and timesheets. Use it when onboarding/offboarding employees, activating synced QBO users, or changing permissions. Before giving exact setup steps, confirm: Is the user created in Lexul directly or synced from QuickBooks? What permission level is required. Then explain the recommended configuration, test with a sample record, and note this guardrail: Only OfficeAdmin can add/edit users; QBO/QBD employees with email sync as inactive users until activated.

Configure when

onboarding/offboarding employees, activating synced QBO users, or changing permissions.

Ask before answering

Is the user created in Lexul directly or synced from QuickBooks? What permission level is required?

Dependencies

• active users
• time types
• permission roles

Role workflow

Admin configures users/permissions; managers review access; field users use assigned views only.

Permissions and visibility

Admin-only for user creation, permissions, active/inactive status, and crew setup.

Known limits and guardrails

Only OfficeAdmin can add/edit users; QBO/QBD employees with email sync as inactive users until activated.

Escalation rule

Escalate if data is missing after sync, accounting source-of-truth is unclear, or the user asks for accounting treatment. Escalate security/access changes that the requester may not be authorized to make.

Source URLs

• https://help.lexul.com/en/articles/6801686-user-management
• https://help.lexul.com/en/articles/8321678-user-level-permissions
• https://help.lexul.com/en/articles/7888533-quickbooks-online-field-mapping

Default response pattern

For questions about Users, users are visible in a table view (First Name, Last Name, Email, Permi..., first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.

Knowledge Record: Users / Crews

record_id: LFS-users-crews

primary_intents:

• how_to_setup
• when_to_use
• workflow_design
• troubleshooting
• permissions_visibility

Sample user utterances

• How do I set up Crews in Lexul?
• When should we use Crews?
• Why is Crews not working or not showing?
• Can Lexul handle Crews for our workflow?

Entities to extract

• user_role
• workspace
• feature_area
• technician_name
• foreman_name
• crew_name
• time_type

Approved answer basis

Crews group technicians under a foreman for simpler scheduling and crew timekeeping. Use it when field teams work together and a foreman should track time for the crew. Before giving exact setup steps, confirm: Who is the foreman, who are crew members, and do they belong to another active crew. Then explain the recommended configuration, test with a sample record, and note this guardrail: Only one active crew per foreman; a technician can only be assigned to one crew at a time; avoid changes during active time logging.

Configure when

field teams work together and a foreman should track time for the crew.

Ask before answering

Who is the foreman, who are crew members, and do they belong to another active crew?

Dependencies

• active users
• time types
• permission roles

Role workflow

Admin configures users/permissions; managers review access; field users use assigned views only.

Permissions and visibility

Admin-only for user creation, permissions, active/inactive status, and crew setup.

Known limits and guardrails

Only one active crew per foreman; a technician can only be assigned to one crew at a time; avoid changes during active time logging.

Escalation rule

Escalate security/access changes that the requester may not be authorized to make.

Source URLs

• https://help.lexul.com/en/articles/6927564-creating-and-managing-crews
• https://help.lexul.com/en/articles/8321678-user-level-permissions
• https://help.lexul.com/en/articles/8283579-timesheet-management

Default response pattern

For questions about Crews, first identify whether the customer is asking about setup, fit, workflow design, troubleshooting, permissions, or QuickBooks sync. Use the approved answer basis above, ask only the listed clarification question when needed, and end with the escalation rule when the issue cannot be resolved from documented checks.