Документация

Checklists: More Than Just a List

In ChecklistGuro, a Checklist is a structured, actionable sequence of steps designed to ensure process standardization.

While a standard Task Description is simply a place for free-form notes, a Checklist functions as a "Smart Form." It allows you to capture specific data points, validate inputs, and ensure that every step of a workflow is completed according to your organizational standards.

Building Your Checklist

Checklists are built using various input elements tailored to your specific needs. When creating a checklist, you can choose from several element types to capture precise information:

• Question & Answer: Simple Yes/No or multiple-choice prompts.
• Text Fields: For capturing detailed notes or observations.
• Number: For recording measurements, quantities, or counts.
• Date & Time: To log exactly when an action occurred.
• Signature: To ensure accountability and formal sign-off.

How to Create a Checklist

1. Navigate to the Checklists module in the sidebar.
2. Click the + Create button.
3. Add your desired elements (Questions, Text, Date, etc.) based on the purpose of your form.
4. Click Save .

Advanced Capabilities

Using Checklists as Digital Forms

Checklists are perfect for transforming manual paper forms into digital, error-proof workflows. By utilizing input types like checkboxes, dropdown menus, and date pickers, you can use Checklists for:

• Safety Inspections
• Quality Assurance (QA) Audits
• Employee Onboarding
• Site Inspections

Ensuring Data Integrity (Mandatory Fields)

To prevent skipped steps, Administrators can set specific checklist items as "Required." When an item is marked as required, the system will prevent a user from marking the parent Task as "Complete" until all mandatory data has been entered and all items have been addressed.

Reusability with Templates

Don't reinvent the wheel every time. Checklists can be saved as templates . You can create a "Master Checklist" and apply it to any new task or project. This is ideal for recurring workflows such as weekly audits, monthly maintenance, or standardized client onboarding.

Automation Triggers

A completed Checklist can act as a "trigger" for your entire Work OS. Using Work OS Automations , you can program the system to react the moment a checklist is finished.

Examples of Checklist-driven Automations:

• Status Updates: Once a "Final Review" checklist is checked off, automatically change the Task Status to "Approved."
• Instant Notifications: Automatically @mention a manager when a critical inspection is completed.
• Workflow Routing: Automatically move a task to a different department's Workspace once the checklist requirements are met.

Mastering Tasks in ChecklistGuro

Tasks are the fundamental building, the building blocks of your workflow. Whether you are managing a single checklist or orchestrating complex construction site inspections, Tasks allow you to track progress, assign responsibility, and automate your entire Work OS.

Understanding Task Fundamentals

At its core, a Task is a single unit of work consisting of two essential elements:

• A Checklist: The specific steps required for completion.
• An Assignee: The person responsible for the work.

Beyond simple checklists, Tasks are highly interconnected. You can link tasks to Files, Model Entries, Processes, and Reports to ensure all necessary context is available in one place.

How to Create a Task

1. Navigate to the Tasks tab in the left-hand sidebar.
2. Click the + Create button.
3. Fill in your task details (Title, Description, etc.).
4. Click Save .

Managing Deadlines

To ensure timely completion, you can set specific deadlines. Within the task details, click the Due Date field to open the calendar picker. You can select both the specific date and the exact time for task completion.

Assigning Responsibility

Assigning work is simple and can be done in two ways:

• Via Task Details: Open the task, locate the Assignee/Responsible field, and select a team member from the dropdown menu.
• Via Team View: For a visual approach, simply drag and drop a task directly onto a user's avatar in the Team View.

Finding Your Work

If you are looking for work assigned to you, check your Home page or the My Tasks dashboard. Note: If a task is missing, please verify that you have the necessary permissions to view that specific Project or Workspace.

Integrated Construction Management

ChecklistGuro is designed to break down silos. You can link a task directly to items in your Construction Management module using the "Relations" field. This allows you to search for and attach specific assets, site inspections, or equipment logs directly to a task.

Automated Workflows

Transform your manual processes into automated engines using Work OS Automations :

• Trigger Actions: You can set rules so that completing a task (e.g., a "Safety Inspection") automatically triggers a new item in another module (e.g., an "Issue Report").
• Process Automation: Navigate to the Processes module to create "If/Then" rules. For example: "If a task status changes to 'Blocked,' then automatically notify the Project Manager."

Processes & Automations: Engineering Your Workflow

A Process (or Workflow) in ChecklistGuro is an automated sequence of actions triggered by a specific event. Processes allow you to instruct the platform to perform complex, multi-mode tasks automatically - such as creating reports, updating statuses, or calculating values - whenever your predefined conditions are met.

How It Works: Triggers & Logic

Every automation begins with a Trigger . A trigger is the "starting gun" that tells a process to run. Triggers can be:

• System Events: e.g., "When a New Task is Created" or "When a Checklist is Completed."
• Scheduled Time: e.g., "Every Monday at 9:00 AM."
• Manual Action: A button click by a user.

Creating Conditional "Branches"

Using the Logic element, you can move beyond simple linear steps and create intelligent, branching workflows. By using IF/THEN statements, your processes can make decisions.

Example:“ IF the task priority is High, THEN create an urgent task for the Manager; ELSE simply update the status to Low Priority.”

The Building Blocks: Process Elements

Processes are constructed by chaining together Process Elements . Each element is a functional building block that performs a specific action.

Pro-Tip: The Power of Entry Get

The Entry Get element is the secret to sophisticated automation. It allows a process to "reach out" and grab information from one part of your system (like a client's email address or a project deadline) and use that data in a subsequent step, such as sending an automated email or updating a task.

Advanced Automation Concepts

Chain Reactions (Process Cascading)

Automation doesn't have to stop with one process. You can create cascading automation where one process triggers another. For example, Process A completes a task, which triggers Process B to generate a report, which then triggers Process C to email that report to a stakeholder.

Automated Reporting

Eliminate manual paperwork by using the Report Create element. You can design workflows that automatically compile data from completed tasks into a polished, professional report at the end of every week or month.

Troubleshooting & Error Handling

If a process encounters an error (such as trying to update a record that no longer exists), the process will stop at the point of failure. To maintain a healthy automation environment, we recommend:

1. Monitoring your logs: Regularly check for stopped processes.
2. Validating Data: Ensure that Entry Get elements are pointing to valid, active records.

Reports: Turning Data into Insights

In ChecklistGuro, a Report is a structured document that presents captured data in a readable, professional format. While your data lives in Checklists and Models, a Report is the final, rendered view designed for stakeholders, clients, or auditors.

The Anatomy of a Report

To master reporting, you must understand the distinction between the Template and the Report itself. Think of it as a "Mold" and a "Print."

Where does the data come from?

Reports are powered by the information captured throughout your platform via two primary sources:

1. Checklists: Data captured during active inspections, audits, or task completions.
2. Model Entries: Structured data gathered through custom forms and database entries.

Designing Your Templates

The platform is user-driven. If you have the necessary permissions, you can design, save, and reuse templates, allowing different departments (e.g., Safety, HR, or Operations) to have tools tailored to their specific needs.

Building with Elements

You can build highly customized templates using a variety of dynamic elements:

• Text: Use for headings, instructions, or static company descriptions.
• Task Elements: Display specific tasks, statuses, or progress percentages.
• Tables: Ideal for displaying structured, row-based data (perfect for checklist results).
• Media/File: Embed photos, digital signatures, or uploaded documents directly into the document.

Styling & Branding

You are not limited to a single look. Report Templates allow you to adjust Styles to match your corporate identity. You can customize typography and spacing to ensure every report looks professional and aligns with your brand standards.

Automation & Workflow

Reports shouldn't just exist; they should work for you.

Automated Report Generation

Using Processes , you can eliminate manual paperwork. You can set up a trigger so that when a specific event occurs (e.g., a checklist is marked "Complete"), the system automatically generates a report.

The Report Create Element

Within a Process, you can use the Report Create element to automate your entire workflow.

• Example Workflow:
  1. Trigger: A Safety Inspection is submitted.
  2. Action: The Report Create element pulls the inspection data.
  3. Result: A formatted PDF is automatically generated and emailed to the Site Manager.

Pro-Tip: When updating a Template , remember that it will only affect future reports. Existing reports are "frozen in time" and will always retain the layout they were originally created with.

Dashboards: Your Centralized Command Center

A Dashboard in ChecklistGuro is a high-level visualization layer designed to aggregate, transform, and display your data in a single, unified view. Instead of clicking through individual tasks or lists, Dashboards allow you to see the "big picture" of your operations at a glance.

Management vs. Analysis

It is important to distinguish between the two primary ways you interact with data in the platform:

• List View (Management): Designed for action . You use a List View to manage specific items, such as checking off a task or updating a model entry.
• Dashboard (Analysis): Designed for insight . You use a Dashboard to analyze trends, such as seeing how many tasks are overdue across your entire organization.

Data Sources & Visual Elements

Dashboards are highly flexible. You can pull data from almost any corner of the platform to create a customized view.

What can I display?

You can populate your Dashboard using data from:

• Tasks & Checklists: Track progress, deadlines, and completion rates.
• Model Entries: Visualize custom data sets and structured information.
• Files & Documents: Monitor recent uploads or important documentation.
• Users & Groups: Track activity and membership within your organization.

Visualization Options

Choose the visualization that best tells your story. You can mix and match these elements on a single dashboard:

Pro-Tips for Success

1. Create Tiered Dashboards

Don't try to put everything on one screen. We recommend a tiered approach:

• Executive Dashboards: High-level summaries for leadership (e.g., "Total Compliance Rate").
• Operational Dashboards: Detailed views for team leads (e.g., "Tasks Due This Week").
• Team Dashboards: Task-specific views for field workers (e.e., "My Pending Inspections").

2. Use Powerful Filtering

Every element on your dashboard can be filtered. You can drill down into your data by filtering for specific Users, Groups, Date Ranges, or custom Model attributes. This allows you to transform a "Global View" into a "Department-Specific View" in seconds.

3. How to Build an Element

Creating a new widget is simple:

1. Open your desired Dashboard and click Edit .
2. Select Add Element and choose your visualization type (e.g., Chart or Table).
3. Select your Data Source (e.g., a specific Task List or Model).
4. Apply Filters to refine the data (e.g., "Only show tasks assigned to Group A").
5. Save your changes.

Data Models: The Foundation of Your Workflow

Data Models are the structural backbone of Checklist. While features like Dashboards and Reports visualize your data, Data Models define it. A Data Model acts as the blueprint for your business information, determining how data is captured, how it relates to other information, and how it drives automated workflows.

The Anatomy of a Data Model

A Data Model is composed of three core layers: Attributes (the data itself), Relationships (how data connects), and Actions (what the data does).

1. Attributes (Elements)

Attributes are the individual data points you collect. Think of these as the columns in a spreadsheet. You can define various types of elements to ensure data integrity:

• Text & Numbers: For names, IDs, or quantities.
• Dates & Times: For deadlines, timestamps, or schedules.
• Users: To assign ownership or responsibility.
• Dropdowns/Booleans: To standardize inputs (e.g., Yes/No or Status levels).

2. Relationships (The "Glue")

The true power of a Data Model lies in its ability to connect different entities. By using Relational Elements , you can break down silos and create a web of interconnected information:

• One-to-One (1:1): Linking a specific User to a specific Profile.
• One-to-Many (1:N): Linking one Customer to many different Orders.
• Many-to-Many (M:N): Linking many Students to many different Courses.

3. The Interface Layer (Entry Labels)

To make your data navigable, you can define Entry Labels . Instead of seeing a list of raw IDs, you can configure the model to display human-readable names (e.g., instead of seeing "ID_99283" , you see "Acme Corp" ). This ensures that your database remains intuitive for all users.

From Static Data to Active Workflows

A Data Model is not just a passive storage container; it is an active participant in your business logic. Through Actions , you can transform a static record into a trigger for automation.

Implementing Actions

Actions allow you to attach functional buttons to your data records. When a user interacts with a record, they can trigger:

• Process Triggers: Clicking a button to launch a new Checklist or Workflow.
• Status Changes: Updating a record from "Pending" to "Approved."
• Document Generation: Triggering the creation of an Invoice or Report based on the record's data.

Pro-Tips for Data Modeling

Summary: If the Dashboard is the window through which you view your business, the Data Model is the foundation upon which the entire building stands. Build it with precision, and your automation will follow seamlessly.

Model Entries: Your Operational Workspace

While a Data Model defines the structure (the template), a Model Entry is the actual data living within that structure.

If you are familiar with Excel, think of the Model as the column headers and the Model Entry as a single, unique row of data. If your model is "Employees," then "John Doe" is a Model Entry. Every piece of information in ChecklistGuro is stored within these individual, actionable records.

Key Features of a Model Entry

A Model Entry is much more than just a static row in a database; it is a collaborative workspace containing several powerful features:

1. Version Control & History

Every time a change is made to an entry, the system tracks it. You can view the Version History to see exactly what was modified, allowing for a complete audit trail. This is essential for compliance and for understanding how a record has evolved over time.

2. Collaboration via Comments

Each entry contains a dedicated space for Comments . This allows team members to discuss specific records, assign tasks, or leave notes without leaving the context of the data. This turns every entry into a thread of communication, ensuring that the "why" behind a data change is never lost.

3. Integrated File Management

Every entry serves as a hub for related documentation. You can attach files directly to an entry, ensuring that all supporting evidence (like photos, PDFs, or receipts) stays organized and contextually linked to the relevant data.

4. Actionable Workflows

Through Actions , a Model Entry can trigger broader processes. Whether it is clicking a button to approve a request or triggering a new workflow, the entry is the engine that drives your business processes forward.

The Ecosystem: Entries & Files

The relationship between entries and files is fluid and highly organized:

• Contextual Attachments: You can attach files directly to an entry so that all relevant documentation is found in one place.
• Centralized File Library: While files are often attached to specific entries, they are also part of a larger, searchable ecosystem.
• Cross-Referencing: A single file can be linked to multiple entries. For example, a "Safety Manual PDF" can be attached to every "Inspection Entry" across your entire organization.

Summary Table: Model vs. Entry

Overview

The Files section serves as the centralized repository for all documents and media uploaded within the Work OS. It acts as a single source of truth, ensuring that all assets attached to various workflows are easily accessible in one location.

File Upload Methods

Files can enter the system through three primary channels:

• Manual Upload: Users can directly upload files from their local device into the Files section.
• Checklist Integration: When a file is attached to a specific item within a Checklist , it is automatically indexed in the Files section.
• Process Automation: Files generated or attached as part of a Process workflow are automatically captured and stored in the Files section.

General Usage

Where can I find all my uploaded documents?

All documents, regardless of where they were originally uploaded, can be found in the Files section.

How can I search for a specific file?

You can use the search bar located within the Files section to search by filename. To refine your search, you can use available filters such as file type, upload date, or the source (Process/Checklist).

Can I organize my files into folders?

Yes, you can create custom folders to categorize your assets.

How do I delete a file?

To delete a file, select the file in the Files section and click the Delete icon.

Warning: Deleting a file will also remove its attachment from the associated Checklist or Process.

Who has permission to view my files?

File visibility is governed by your workspace's permission settings. Typically, any user with access to the specific Process or Checklist where the file was uploaded will also have visibility of that file in the Files section.

What file formats are supported?

The platform supports all standard file types, including but not limited to:

• Documents: .pdf, .docx, .txt, .rtf
• Data: .csv, .xlsx, .json
• Images: .png, .jpg, .jpeg, .gif

Is there a maximum file size limit?

There is no file size limitation.

Messages: Your Central Communication Hub

In a fast-moving business environment, information shouldn't be trapped in emails or external apps. Messages is ChecklistGuro’s integrated communication engine, designed to keep your team connected, informed, and aligned - all without ever leaving the platform.

Whether you need to send a quick update, share a critical document, or host a real-time strategy session, Messages provides the tools to collaborate instantly.

Multi-Functional Communication Tools

Messages is more than just a texting app; it is a multi-functional workspace that supports various modes of interaction:

• Text Messaging: Quick, asynchronous communication for rapid updates and status checks.
• File Sharing: Send documents, images, and media directly within your chats. By sharing files within the context of your work, you ensure that project-related information remains easy to find and never gets lost in an external email thread.
• Voice Calls: Need an immediate answer? Initiate a direct voice call with a colleague instantly through the platform.
• Live Meetings: For complex discussions that require face-to-face interaction, you can create and join Live Meetings (video conferencing) directly within the app, enabling real-time visual collaboration.

Chat Types: 1-to-1 vs. Group Chats

Depending on the complexity of your discussion, you can choose between two distinct communication environments:

1-to-1 Chats

Designed for private, direct communication. Use 1-to-1 chats for sensitive information, quick check-ins, or individual coaching between you and a single colleague. You can start these by simply searching for a specific team member.

Group Chats

Designed for team-wide collaboration. Group chats serve as dedicated workspaces where multiple participants can communicate, share files, and discuss ongoing projects together. These are ideal for project squads, department-wide updates, or managing specific task groups.

Why Use Messages within ChecklistGuro?

Integrating your communication directly with your data and workflows offers three major advantages:

1. Contextual Continuity: You don't have to switch between "Work" and "Chat." Everything happens in one ecosystem.
2. Reduced Information Silos: By sharing files and discussing tasks within the platform, the "source of truth" remains centralized.
3. Increased Speed: The ability to move from a text message to a voice call, or from a chat to a Live Meeting, allows your team to resolve issues in real-time.

Pro-Tip

Keep the history clean. Use Group Chats for project-specific discussions and 1-to-1 Chats for personal coordination. This ensures that when a new team member joins a project, they can review the group chat history and get up to speed instantly.

Offline Mode: Uninterrupted Productivity

In many industries - from remote field inspections to basement utility checks - internet connectivity is never guaranteed. Offline Mode in ChecklistGto ensures that a lack of signal never results in a lack of productivity.

Depending on your operational needs and user roles, ChecklistG ensures that your data is captured accurately, whether you are in a high-rise office or a remote field site.

Two Tiers of Connectivity

We provide two distinct modes of offline operation, designed to balance data safety with operational autonomy.

1. Default Mode: The "Safety Net" (Default)

Best for: Office-based users or those with intermittent connectivity.

The Default mode acts as a buffer against unexpected connection drops. It is designed to protect you from data loss during "dead zones."

• How it works: It keeps the connection live as long as possible. If your signal drops unexpectedly, the system captures your changes locally.
• The Sync Process: Once your connection is restored, the system automatically pushes your cached changes to the server.
• Limitation: You must have an active connection to load new tasks or view data you haven't previously accessed.

2. Advanced Mode: The "Full Autonomy" (Advanced)

Best for: Field technicians, remote inspectors, and users in "dead zone" environments.

The Advanced mode is a proactive strategy for users who operate in environments with zero connectivity. It allows for true, independent work.

• How it works: This mode pre-downloads all necessary assets to the device before the user leaves the network.
• Capabilities: Users can start new tasks, view previously loaded data, and complete complex checklists without any internet signal.
• The Sync Process: Like the Default mode, all work is queued locally and automatically synchronized the moment the device reconnects to the network.

Comparison at a Glance

Administration & Configuration

The ability to use Advanced Mode is managed at the administrative level. Administrators can configure specific users or roles to ensure the right people have the right tools for their environment.

Administrators can control:

• Targeted Users: Assign Advanced Mode capabilities to specific roles (e.g., "Field Technicians").
• Data Scope: Define which specific Checklists or Model Entries should be pre-downloaded.
• Sync Frequency: Set parameters for how often the device should attempt to refresh its local database.

Pro-Tip for Field Teams: Always ensure your devices are fully synced and all required checklists are loaded before departing the office or a Wi-Fi zone to ensure a seamless transition to the field.

User Management & Profiles

In ChecklistGuro, Users are the individuals granted access to your account. To ensure security and organization, every user is assigned a unique digital identity and specific permissions. This allows you to control exactly who can view, edit, or manage your workflows and data.

The User Profile

A User Profile is more than just a login; it is a unique digital identity used to track accountability across the platform. Every profile contains essential information, including:

• Full Name & Job Title
• Email Address
• Department
• Profile Picture

This information is used globally to identify contributors in task assignments, comments, and automated workflows.

Managing Your Own Profile

Users have full control over their personal presence within the platform. By visiting your Profile Settings , you can:

• Update your identity: Change your display name or profile picture.
• Customize Notifications: Manage how and when you receive alerts. You can toggle settings for Email , In-App Notifications , and Desktop Push Notifications for specific events like task assignments or mentions.

Administrator Functions

Inviting New Users

Administrators have the power to grow the team. To add a new member:

1. Navigate to the Users management page.
2. Click the "+ Add User" button.
3. Enter the person's email address.
4. Assign a Role: Before sending the invite, you must select a permission level (e.g., Admin, Manager, or Viewer).

Roles & Permissions

To maintain security, every user is assigned a specific role. While the specific permissions depend on your organization's setup, roles generally follow this hierarchy:

• Admin: Full access to user management, system settings, and all data.
• Manager: Ability to create tasks, manage workflows, and oversee team progress.
• Member/Worker: Ability to view assigned tasks, update statuses, and interact with workflows.

Troubleshooting & Access

Lost Access or Password Reset

If you are unable to log in, navigate to the login screen and use the "Forgot Password?" link. An automated reset link will be sent to your registered email address.

Account Issues

If you are locked out of your account or experiencing persistent login issues, please contact your Internal Workspace Administrator . They have the authority to reset credentials, verify account status, and manage your access permissions.

Pro-Tip for Admins

When inviting new users, always double-check the assigned Role . Assigning "Admin" rights to everyone can lead to accidental changes to your core workflows!

Groups: Scaling Your Administration

In ChecklistGuro, Groups are collections of Users bundled together for administrative efficiency. Instead of manually assigning permissions to every new hire, you assign permissions to a Group .

Any user added to that Group automatically inherits all the associated permissions, roles, and settings.

The Hierarchy of Access

To manage a large organization effectively, it is important to understand how Users, Groups, and Roles interact. Think of it as a three-tier hierarchy:

1. User: The individual identity (e.g., "Alice" ).
2. Group: The container for users (e.g., "Marketing Team" ).
3. Role: The set of specific permissions (e.g., "Can Create Checklists" ).

The Workflow: You assign Roles to a Group , and then you place Users into that Group .

Why Use Groups?

Reducing "Permission Bloat"

Manually configuring every individual user leads to "Permission Bloat" and human error. By using Groups, you ensure consistency. When a new employee joins the Marketing team, you simply add them to the "Marketing" group; they instantly receive access to all necessary folders, tools, and workflows without a single manual configuration.

Additive Permissions

ChecklistGuro follows the principle of Additive Permissions . If a user belongs to multiple groups, their permissions are cumulative.

• Example: If Group A grants "View" access and Group B grants "Edit" access, a user in both groups will have "Edit" access. Permissions are never subtracted by joining a new group; they are only added.

Managing Your Groups

Group Types & Best Practices

To keep your organization organized, we recommend categorizing your groups into two types:

Pro-Tip: Use Functional Groups for general communication and Access Groups for controlling sensitive data.

How to Modify Group Membership

You can manage users within a group through two different methods:

1. Via the Groups Menu: Navigate to the Groups section in your dashboard, select the group, and use the "Add/Remove" interface.
2. Via the User Profile: Navigate to an individual User's Profile and update their group memberships directly.

A Note on External Guests

You can add External Guests to specific groups. However, we recommend creating dedicated "Guest Groups" to ensure that contractors and clients do not accidentally inherit permissions from your internal, high-security functional groups.

Roles: Defining Capabilities

In ChecklistGuro, a Role is a predefined set of permissions and capabilities. While a Group defines who a person is, a Role defines what they are allowed to do within the platform (e.g., View, Create, Update, or Delete).

Permissions vs. Roles

Understanding the distinction between these two is critical for effective administration:

• Permission: The smallest, atomic unit of access. Examples include can_delete_task or can_view_report .
• Role: A collection of many Permissions bundled into one easy-to-manage package. For example, a "Manager" role might bundle can_edit_task , can_assign_user , and can_view_reports .

By using Roles, you avoid the complexity of managing hundreds of individual permissions for every user.

Managing Permissions

Custom Roles

You are not limited to system defaults. If your organization has highly specialized workflows, you can create Custom Roles . To do this, navigate to the Roles section and click "Create." From there, you can hand-pick specific permissions to build a role tailored exactly to your needs.

The "Template" Effect

It is important to remember that Roles act as templates. If you modify an existing Role (e.g., adding a new permission to the "Editor" role), that change is instant and global . Every User and every Group assigned to that role will immediately receive the new capability.

The Principle of Least Privilege (PoLP)

ChecklistGuro follows "Most Permissive" logic. If a user's various permissions conflict, the platform defaults to the highest level of access.

• Example: If one assigned role allows "View" and another allows "Delete," the user will be able to Delete .

Best Practice: We strongly recommend following the Principle of Least Privilege (PoLP) . Only grant the minimum roles and permissions necessary for a user to complete their specific job functions. This minimizes the risk of accidental data deletion or unauthorized changes.

How Roles Interact with Users and Groups

To maintain a scalable system, you must understand how access flows through the platform.

One User, Multiple Roles?

Technically, a single User identity is assigned only one primary role. However, because a User can belong to multiple Groups , and each Group can have its own Role, a user can effectively inherit many different roles and permissions simultaneously.

The Efficient Workflow: Roles $\rightarrow$ Groups $\rightarrow$ Users

The most efficient way to manage ChecklistGuro is to assign Roles to Groups rather than to individuals.

Account: Your Global Control Center

The Account section is the administrative core of your ChecklistGuro environment. Unlike Data Models or Entries, which govern specific processes, the Account settings provide global configuration for your entire workspace.

This is where you manage the high-level identity, security, billing, and branding of your platform. Changes made here are environment-wide and define the foundational experience for every user in your organization.

Branding & Interface Customization

Tailor the platform to reflect your company’s identity and meet your team's linguistic needs. Within the Account settings, you can manage:

• Language Support: Define which languages are available for your users, ensuring accessibility for global teams.
• Typography & Styling: Customize the global font and visual themes to align the platform with your corporate branding.
• Workspace Identity: Update your workspace subdomain to reflect any changes in your company branding.

Administration & Integrations

Manage the technical foundation and connectivity of your workspace:

• API & Automation: Generate and manage API Keys to integrate ChecklistGuro with your existing tech stack and automate workflows.
• Security & Access: Oversee high-level security configurations to ensure your data remains protected.
• System Limits: Monitor and manage system-wide parameters, such as maximum file upload sizes, to optimize performance and storage.

Subscription & Billing

Maintain full control over your service level and continuity:

• Plan Management: Upgrade or downgrade your subscription plan to match your growing organizational needs.
• Billing History: Access and download invoices and manage your payment methods to ensure uninterrupted service.

Critical Information

Permanent Actions Deleting an account or making significant structural changes to your workspace settings is permanent . Always ensure you have backed up necessary data and consulted with your stakeholders before executing high-level administrative changes.

Subdomain Changes Changing your workspace subdomain will alter the URL used to access your platform. This may break existing bookmarks, saved links, or third-party integrations. Plan these changes during low-activity periods.

Profile: Your Personalized Workspace Identity

The Profile section serves as the individualized interface for every user within the ChecklistGuro ecosystem. While the Account section manages the global, organizational-wide settings, the Profile section is dedicated to your personal user experience and individual operational preferences.

This is where you define how you interact with the platform, manage your personal notifications, and customize your digital identity within your team's workspace.

Identity & Personalization

Manage how you are represented to your colleagues and how you interact with the platform's interface:

• User Identity: Update your profile picture (avatar) and display name to ensure clear identification in task assignments, comments, and audit logs.

• Personalized Bio: (Optional) Provide a brief professional summary to help teammates understand your role and expertise within the organization.

• Timezone & Localization: Configure your personal timezone and preferred date/time formats. This ensures that all deadlines, task due dates, and activity logs are synchronized with your local working hours, preventing scheduling conflicts.

Notification & Alert Management

Control the flow of information to prevent "notification fatigue" and ensure you only receive high-priority updates:

• Email Preferences: Define which platform activities trigger an email notification (e.g., direct mentions, task assignments, or system announcements).
• In-App Notifications: Customize the behavior of the platform's real-time alert system, allowing you to manage how desktop or browser-based notifications are delivered.
• Digest Settings: (If applicable) Configure daily or weekly summary digests to review all platform activity in a single, organized communication.

Security & Personal Authentication

Manage the credentials and security layers that protect your individual access:

• Credential Management: Update your password and manage secondary authentication methods to maintain the security of your user account.
• Multi-Factor Authentication (MFA): Configure and manage your personal MFA settings to add an essential layer of security to your login process.
• Session Management: Review and manage active sessions to ensure that your account is only being accessed from authorized and recognized devices.

Critical Information

Security Awareness Never share your Profile credentials or MFA recovery codes with anyone. [Platform Name] administrators and support staff will never ask you for your password.

Support & Service Framework: Your Gateway to Resolution

The Support section is the formal communication layer between your organization and the ChecklistGuro engineering and success teams. While the Account and Data sections govern your internal operations, the Support framework provides the external mechanism for technical escalation, platform maintenance reporting, and continuous improvement.

This is the centralized hub for all outbound inquiries, ranging from critical system bug reports to strategic feature requests.

Support Modalities

Our support ecosystem is structured into three distinct channels, each designed to address specific levels of technical urgency and complexity:

1. Technical Incident Reporting (Bug Reports)

When the platform deviates from its intended behavior, the Bug Reporting channel allows you to trigger a technical investigation.

• Incident Scrutiny: To ensure rapid resolution, our engineers require detailed reproduction steps, system logs, or visual evidence (screenshots/recordations) to diagnose the root cause.
• Priority Routing: Critical bugs—those impacting workspace stability or data integrity—are automatically escalated through our high-priority deployment pipeline.

2. General Inquiries & User Assistance

For questions regarding platform capabilities, workflow optimization, or "how-to" guidance, the General Inquiry channel provides direct access to our Support Specialists.

• Functional Guidance: Use this channel to clarify complex configurations or to understand how new platform updates impact your existing workflows.
• Response SLA: We adhere to a standardized Service Level Agreement (SLA), aiming to acknowledge all non-critical inquiries within 24-48 business hours.

3. Product Evolution (Feature Requests)

The Support framework serves as a feedback loop for our product development lifecycle.

• Innovation Feedback: Users can submit structural suggestions and feature requests that are reviewed by our Product Management team during our roadmap planning cycles.
• Continuous Improvement: Your feedback directly informs the evolution of the ChecklistGuro ecosystem.

Critical Support Protocols

Service Level Expectations

All support requests are processed in the order they are received, prioritized by impact. While we strive for rapid resolution, the complexity of certain technical inquiries may require extended investigation periods.

Information Security & Privacy

When submitting support tickets, users are reminded to adhere to our Data Privacy Policy .

• Sensitive Data: Never include plain-text passwords, API keys, or highly sensitive PII (Personally Identifiable Information) within a support description or attachment.
• Secure Attachments: If a technical issue requires the sharing of logs, please ensure all sensitive identifiers are redacted prior to submission.

Incident Management

In the event of a platform-wide service disruption, the Support team will communicate updates by email.