How Cove and Visitt work

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Users can be added one at a time (first name, last name, company, login email and role), by CSV bulk upload, or by self-enrollment through a tenant's email domain. Self-enrolled users always start as Regular Users and lose access when they lose that work email.

Adding Users · Manually Adding A User

Exception / edge case: Bulk upload, for Building Admins and Building Managers, fails unless tenant names exactly match the directory, including case and symbols, and roles use exact codes such as tenant-admin. Headers must not change. A preview shows new, cross-site and skipped users with reasons, and no invitation messages are sent.

Bulk User Upload & Formatting Guide

Documented behavior: Building Admins can configure every module; Building Managers differ mainly in not configuring Work Orders. Engineering Managers configure maintenance, Security and Reservation Managers cover visitors and bookings, Tenant Admins can submit work orders and register visitors, Tenant Hosts only register guests, and Regular Users can do neither.

User Roles

Exception / edge case: Regular users with dashboard access receive no dashboard login code until they first sign in through the mobile app. At sites with an access control integration, users also need a matching profile in that system.

Adding Users

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Building Admins and Building Managers add leases on a tenant's Leases tab with start date, end date or a Month-to-Month flag, billing lease code, floors and suites, one record per suite. Properties with the RentRoll integration get leases created and updated nightly from the file instead.

Managing Tenant Leases

Documented behavior: A work order takes the billing lease code of the lease linked to its suite, falls back to the billing ID on the tenant profile, and otherwise gets none, which can block billing verification and Yardi exports. The code is fixed when the ticket is created or last saved; re-saving re-evaluates it.

Managing Tenant Leases

Exception / edge case: Archive ended leases rather than delete them: two active leases on one suite can apply the wrong code. RentRoll creates month-to-month leases from blank end dates only if Allow Month-to-Month Lease Creation is on, and archives them when they drop out of the file.

Managing Tenant Leases

Limitation / verification point: Cove's tenant offboarding article repeats its staff-suspension guidance (suspend rather than delete, to keep history), and the article on adding tenant organizations is no longer public, so tenant-organization creation and closure steps are not recorded here.

Best Practices for Offboarding Tenants · Adding and Managing Tenant Organizations

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: A Tenant Admin can manage users only after a Building Admin or Building Manager ticks User Manager on their profile. User Managers can add users, switch roles between Regular User, Tenant Host and Tenant Admin, appoint other User Managers and suspend or reactivate accounts.

Tenant Admin User Manager

Documented behavior: Property teams can switch off tenant user management with Disable Tenant User Management in Property Info, which hides the User Manager option so all user changes go through the property team. A new user needs only first name, last name, login email and role.

Tenant Admin User Manager

Exception / edge case: Suspending logs the user out immediately and blocks the app, dashboard and mobile building access, but keeps waivers, reservations, attendance and work order history attached for reporting. Suspended users are hidden from the directory unless filtered for, and can be suspended in bulk.

Suspend or Unsuspend Users · Best Practices for Offboarding Users

Documented behavior: Before suspending a staff member, Cove advises removing them from work groups and routing rules for work orders, maintenance and inspections, and from notification emails in Property Info, amenities and Visitor Setup, so assignments and alerts are not lost.

Best Practices for Offboarding Users

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Cove creates buildings during onboarding; property teams add floors, suite types and suites manually or by CSV, which creates but never updates records. Suite type visibility (Shared, Tenant or Internal) controls who can raise work orders in a suite and drives inspection routing.

Buildings, Floors, And Suites

Exception / edge case: Suites must be removed before their floor, and floors before their building. Deleting a suite removes it from tenants and future use but keeps past work. A separate building address makes visitor invitations show that building rather than the site address.

Buildings, Floors, And Suites

Documented behavior: Property Info holds timezone, currency, default amenity hours and closure dates, logos, notification emails, per-category email sender names, enrollment approval, profile-editing and tenant user management switches, and billing settings such as remit-to address, billing period and cross-site credit use.

Property Info

Exception / edge case: A closure date blocks new bookings on every reservable amenity for the whole day but does not cancel existing reservations; staff must review them. Building Admins and Managers can override closures.

Property Info

Documented behavior: The dashboard-only Resources page, enabled by Cove, shows property hours and PDF handbooks up to 20 MB, each visible to all tenants or chosen user tags. The site short name in Property Info sets the branded login addresses at manage.cove.is and mybuilding.cove.is.

Resources Page · Create a Custom URL for Your Web Dashboard

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: The home screen is built from sections: Row sections show highlights as tiles, Spotlight sections show full-width carousels with an optional call-to-action button. A section can be hidden, and sections or individual highlights can be limited to chosen user tags.

Highlights: Creating & Managing Mobile Highlights · App Spotlights

Documented behavior: A highlight always has an image, title and description, and can add a web link, phone number, an inquiry form emailed to staff, or a link to an in-app feature. Highlights also feed building displays, and the highlight list can be exported to CSV.

Highlights: Creating & Managing Mobile Highlights

Exception / edge case: Additional app screens are invisible until linked from a home-screen highlight, and a highlight section can belong to only one screen. When a Spotlight section holds several highlights, the first one shown is random on each app load.

App Screens · App Spotlights

Documented behavior: Up to four quick action buttons can open an amenity booking, a new service request (optionally for one issue type), visitor management or an external link, optionally in the phone's browser. Each button is shown to all roles or to the internal team only.

Quick Action Buttons

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Tenant Admins submit from the app's Requests tab or quick action and building staff from the Work tab or the dashboard's New Ticket. Buildings can require a due date or extra questions. Equipment can be linked only after choosing building and floor, and staff can set assignee, work groups and extra email recipients.

Submitting a Work Order

Limitation / verification point: Work order attachments accept JPG and PNG images, PDFs and office files, and MP4 video up to five minutes, with several files at once. The public work order form accepts images and PDFs but not video.

Submitting a Work Order · Public Work Orders

Documented behavior: Public work orders, set up with Cove's CSM or Support, let anyone without a Cove account submit after verifying their email with a one-time code. Requests follow normal routing; the submitter's contact details are written into the description and status emails go to the verified address, which staff can change.

Public Work Orders

Permissions: Building Admins and Building Managers configure the Work Order module and create recurring work orders. Tenant Admins and Regular Users can submit and track work orders only if the building has configured them to; users without the option need their admin to set up access.

Work Order Overview

Documented behavior: Make team members assignable and set up work groups before configuring issue-type or category routing. Rules can use a default for all buildings or building-specific assignments within a campus.

Work Order Assignments and Routing

Limitation / verification point: The guide’s general rule says that when a default assignee and a work group are both selected, the assignee receives notifications while the group retains visibility. Some examples in the same article are inconsistent; verify the actual notification behavior in a demonstration.

Work Order Assignments and Routing

Documented behavior: Building admins can require labor hours, a note and/or mileage before completion. Mileage depends on Travel being enabled. Missing requirements block Complete or Closed transitions on web and mobile. Bulk completion evaluates each work order separately and reports the blocked records.

Work Order Completion Requirements

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Only Building Admins create labor rates and materials. Each carries defaults for billable, tax and tenant markup, an optional fixed or percentage markup that overrides the tenant rate, and cost code rules mapping base, markup or total amounts to GL accounts. Engineers can adjust lines on a work order.

Adding Labor Rates to Your Work Order Library · Adding Materials to Your Work Order Library

Documented behavior: Once labor or materials are on a work order, staff send an estimate from its Invoice tab with a note that appears in the tenant email and the activity log. The estimate becomes Proposed, and the tenant, notified by email and push, can accept it or request changes.

Work Order Estimates

Documented behavior: Work orders with charges move To Close, then Billing Verification, then Closed & Verified, and only verified ones are billed. Cove advises separating whoever adds charges from whoever verifies, and enabling restrictions so verification needs a lease code and cost rules, optionally locking later edits.

Adding Billable Charges & Creating Tenant Invoices

Documented behavior: Tenant statements are produced in Batch Reporting by verification date and can be stored, emailed internally or sent to tenant billing contacts. Single PDF invoices, overviews or statements can be exported from Closed & Verified, and reservation fees are added on the reservation or via a triggered work order.

Adding Billable Charges & Creating Tenant Invoices

Exception / edge case: Charges on a verified work order are corrected with Reverse Charges, which turns every amount negative, keeps the order Closed & Verified and logs one Charges Reversed event. Cove's audit checklist compares the tenant billing report with a billables breakdown to catch missing lease codes or unmapped items.

Adding Billable Charges & Creating Tenant Invoices

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Recurring work order templates are created from Work Order Setup with status, an interval in days, weeks, months or years, a next open date and an optional end date. Each occurrence fires as an ordinary work order and follows the normal category, issue-type and building routing rules.

Recurring Work Orders

Documented behavior: When dated work opens is set site-wide in General Setup (at creation, a set buffer before the due date, or on the due date) and can be overridden per issue type. The per-issue-type mode appears only when Collect Due Date? is checked. Notifications go out when work is scheduled and again when it opens.

Work Order Scheduling

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Only Building Admins create, upload or delete equipment and categories, including bulk delete; engineers, security, building and engineering managers can view and edit records on the dashboard and mobile. Categories can carry custom fields that appear on every item and as table and export columns.

Equipment Libraries

Documented behavior: A task template combines equipment, schedules and steps, with a projection calendar. Procedures are shared step lists whose edits apply to every template using them. A template can have several schedules with different procedures or assignees, skip weekends, or run seasonally in selected months only.

Maintenance Task Templates, Procedures and Schedules · Seasonal Maintenance Schedules

Exception / edge case: Task progress saves automatically and tasks can be put on hold and resumed. Completing without every step requires a reason under Important Notes. Marking equipment inactive excludes it from maintenance schedules when they fire.

Completing Maintenance Tasks · Equipment Libraries

Documented behavior: Open tasks can be batch-assigned or batch-status-changed, for example to On Hold. Completed work is reviewed in Task History with search, filters and sorting, or per item under the equipment's All Task History.

Bulk Assigning and Editing Maintenance Tasks · Maintenance Task History

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: QR codes or existing barcodes must be generated and attached to equipment before linking; any generator works, and Cove's CSM can help with bulk codes. The item must already exist in the equipment library.

Assigning QR Codes to Equipment

Documented behavior: Linking and scanning happen in the mobile building app with camera access: open Equipment, pick the item and tap Link Asset Tracking Code to scan it. Later, Scan on the Equipment page opens the item directly, for example to create an on-demand task.

Assigning QR Codes to Equipment

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Choosing the network in the dashboard's site selector shows Maintenance across all sites, with each task labelled by site. A new task first asks for the site, then uses only that site's data. Batch reassignment lists only users with access to every site in the selection.

Maintenance at the Network Level

Limitation / verification point: At network level, equipment can be viewed and edited but must be created at the site. Only Building Admins can create network procedures, scoped to all or selected sites, and those procedures can no longer be edited at site level.

Maintenance at the Network Level

Documented behavior: Building Engineers assigned to several properties automatically get a Snapshot tab when they select the network in the mobile app: sites listed alphabetically with work order and maintenance counts for me, my groups and all, filterable by type. An AI site summary was still listed as coming soon.

Mobile Engineer Experience

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Inspections are built in three stages: a template with a default recurrence interval and an open-date buffer before the due date, then sections of grouped questions, then an inspection schedule that activates it. The setup articles list the forms' fields only at a high level.

Creating Inspections

Documented behavior: Inspections are listed by assignment (New In My Group, Assigned To Me, Open) with the statuses To Do, In Progress and Completed. Staff complete one section at a time, Start Section then Complete Section, from the dashboard or the mobile Work tab.

Managing Inspections · Viewing and Completing Inspections

Limitation / verification point: Cove's own articles disagree on mobile support: some still label mobile inspections as coming soon, while the completion article (updated July 2026) describes completing them in the mobile app. Confirm current mobile behavior before relying on it.

Creating Inspections · Viewing and Completing Inspections

Documented behavior: Cove separates configured insurance requirements, document extraction and reviewer correction. Its extraction guide retains manual questions and property-specific matching; a reviewed document must be associated with the correct tenant or vendor.

COI Extraction: AI Review

Documented behavior: Each tenant or vendor has one current coverage set and historical sets. Creating a new set archives the previous version with its compliance snapshot; editing current coverage changes that version in place. Current coverage drives compliance and notifications. Separate tabs expose past coverage, documents, requirements, notes and activity.

Coverage Sets and Coverage Versioning

Documented behavior: Purchase Order General Setup controls shipping and billing addresses, additional document language, required approver or vendor signatures and approval-notification recipients. These settings are applied to generated purchase-order PDFs.

Purchase Order Setup

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Incident categories and types (with severity, optional description and optional questionnaire) can be created at network level and limited to specific sites. The module must be enabled by Cove; if it is missing, contact Customer Success or Tech Support.

Incident Setup

Documented behavior: Routing is set per building and per incident type by choosing a work group from the Work Order module, so groups and their notification hours must exist first. The person who creates an incident does not receive its notification.

Incident Setup

Documented behavior: Incidents can be opened from the dashboard or mobile app with category, type, location and optional tenant and attachments. Open covers open and on-hold reports; Resolved covers resolved, cancelled and closed. Each incident keeps a history and chronology, and its status and work groups can be edited.

Incident Response and Management

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Time Cards must be enabled by Cove, then each staff profile needs Can Submit Time Cards? ticked. Property teams define time types such as Standard, Overtime and Vacation, each optionally requiring a note; entries follow the site's time increment, typically 15 minutes, and daily maximum.

Time Cards Setup (Property Teams) · Using Time Cards (Building Team Members)

Documented behavior: Staff record hours in the mobile app under My Labor Hours, by start and stop time or total hours, saving drafts during the week. A submitted week is locked until an approver acts; a denied week comes back editable with the approver's note.

Using Time Cards (Building Team Members)

Exception / edge case: Approved weeks are locked for payroll and cannot be edited in the app. To correct one, the approver denies it for resubmission or adds a separate adjustment entry with an admin note on the dashboard, which the activity log records with who and when.

Time Cards Management (Property Teams) · Using Time Cards (Building Team Members)

Documented behavior: Approvers work from a Needs approval queue of submitted weeks with bulk and inline approve or deny, and a Time Cards list filterable by date, employee, status and site that can be exported for payroll reconciliation.

Time Cards Management (Property Teams)

Documented behavior: Administrators create a category and a reservable space, then configure availability, approval, visibility, payment options and any questionnaires or operational follow-up.

Create an Amenity Space

Documented behavior: Reservation policies are enabled through Cove support or the customer-success manager. Create them at site level, then attach them to individual spaces. A policy can vary booking windows by tenant or user tag. When both restrictions are set, both must match; the highest-priority matching policy wins.

Amenity Space Reservation Policies

Limitation / verification point: Credits are allocated by tenant and billing cycle. The guide distinguishes displayed booking costs from later usage reconciliation and describes potentially confusing cash or invoice messaging when credits are used. Check the configured payment combination and cycle-end export.

Understanding and Managing Credits in Reservations

Limitation / verification point: The current property-team guide supports entering several dates together, while retaining separate reservation records. Test later edits, cancellations and charges for the whole series instead of assuming they behave as one record.

Reserving Amenities: Property Teams

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: The RSVP limit counts people, not bookings, and a per-user limit allows plus-ones. With a waitlist, users can be auto-promoted oldest first and optionally made to confirm within a set time or drop to the bottom; otherwise staff convert them manually, which sends no email. Waitlisted users cannot be checked in.

Creating & Managing Events

Documented behavior: Recurring events use a template with an interval and an Advance Open Window that controls how far ahead each occurrence is created, and so becomes visible in the app and on displays. Template changes affect only occurrences not yet created, and each created event can be edited individually.

Recurring Events

Limitation / verification point: RSVP Slot events let users book a labelled time slot with optional capacity, but slot events have no waitlist. Ticket prices need Stripe, publishing to displays needs displays enabled and a landscape image of at least 1344x1080, and a waiver can be required before anyone RSVPs.

Event Type: RSVP Slots · Creating & Managing Events

Documented behavior: Building Admins, Building Managers and Reservation Managers can run check-in on an iPad Cove Kiosk app or kiosk.cove.is, logged in with a Building Admin's email code; guests scan their personal QR code. Each kiosk is set to one event, and switching events means tapping the Cove logo ten times.

Event Check-In Tablet

Documented behavior: Post-event surveys go to all RSVPs or only checked-in users, by push and/or email, either automatically a set time after the event or manually later. Users on older app versions are taken to the event page instead of the survey. Results appear on the event and in Surveys.

Event Surveys

Limitation / verification point: The email-metrics guide documents delivery and user detail. Its wording differs on open-rate availability: one passage presents it as forthcoming, while another describes support-led activation. Treat current entitlement and the exact report as questions to verify.

Track Email Announcement Metrics

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Chat must be enabled for the site by Cove, and every participant, staff and tenant users alike, needs Is Chat Contact? checked on their Directory profile by a Building Admin before they can take part.

Chat: Property Teams · Chat: Tenants

Documented behavior: Building Admins and Building Managers can open a conversation with one or more tenant organizations; each organization gets its own thread that automatically includes all of its Chat Contacts. Tenant Chat Contacts can also start a conversation with the property team.

Chat: Property Teams

Limitation / verification point: Tenants see property-team messages as coming from the building, with no individual sender name, while staff see each tenant sender's first name. Read status and unread badges sync across the dashboard and mobile app in real time.

Chat: Property Teams · Chat: Tenants

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Visitor Setup decides whether Regular Users and Tenant Admins or Hosts may register visitors, the maximum consecutive visit days (up to 365), whether email is required, SMS invitations and host arrival texts, QR codes in invitations, photos, check-out, and badge printing with QR, barcode or logo formats.

Visitor Management Setup

Documented behavior: Visits can be single, up to ten separate dates, or recurring (daily, weekdays or chosen days). With access control, hosts can override the site's default access window. Staff can re-invite past visitors and paste lists; notes for the building stay internal while the host note and reason appear in the invitation.

Visitor Registration: Tenant Admins · Visitor Registration: Property Teams

Documented behavior: Building Admins, Building Managers and Security Managers check visitors in individually or in bulk, by scanning a QR code, driver's license or passport, or automatically at a turnstile. ID scans use only first and last name, fuzzy-matched against today's visitors; Cove does not store birth date or document number.

Checking Visitors In

Exception / edge case: Visitors can be checked in only on their scheduled date and only once. Bulk and turnstile check-ins skip photos and badges. With access control, a failed credential disables check-in and badge printing until retried or re-registered, and Activate on Check-In keeps access off until check-in.

Checking Visitors In

Exception / edge case: Watch list matches are never blocked automatically. Security is alerted when a matching visitor is registered; check-in then requires ticking approval and a mandatory note, which is emailed to watch list recipients. Unregistered walk-ins are not flagged, so staff must search the watch list manually.

Watch List

Documented behavior: Only Building Admins, plus Tenant Admins given permission, edit the watch list. Matching is Sensitive by default (nicknames and small first-name variations, exact last name) or Strict (exact names); a change applies only to visitors created afterwards. Custom threat levels can be site- or network-wide.

Watch List

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: A group visit registers any number of people, each marked Visitor or Vendor, for one date or up to ten dates at once. Each person gets a separate record and credential per date, editable individually afterwards. Host floor appears only if Visitor Settings enable it and the tenant has several floors.

Group Visits

Documented behavior: Bulk upload, for Building and Tenant Administrators, accepts a CSV template (per-guest times, hosts and companies) or a pasted list that shares one date, time and host. Rows with errors are flagged in a preview and are not registered until corrected; a blank host email assigns the visit to the uploader.

Bulk Visitor Uploads

Exception / edge case: Guests need an email or phone number to receive notifications and a mobile pass. The Feb 2025 group-visit article says the feature was live for standard visitor management and coming soon for access-control sites; with access control, a guest's QR code may appear only hours before the visit.

Bulk Visitor Uploads · Group Visits

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Building Admins can revoke a user's HID Wallet passes from the bottom of the user's Directory profile; the Revoke All Wallet Passes button appears only at sites with the HID Wallet integration. It is used for a new or lost phone, or when there are too many passes on one account.

Revoking a User's Wallet Credentials

Exception / edge case: Revoking is immediate, cannot be undone and removes passes on every device on the account. Before revoking, confirm the access-control email exactly matches the Cove login (the most common cause of failed reissues) and that the user is not suspended.

Revoking a User's Wallet Credentials

Documented behavior: After revoking, the user deletes old passes, waits 5 to 10 minutes for HID to sync with the access control system, then sets up mobile access again in the Cove app. Errors about not finding the account mean the emails do not match.

Revoking a User's Wallet Credentials

Limitation / verification point: The captured setup guides for HID Bluetooth, HID Wallet, Kastle Wallet and Swiftconnect contain only section headings, so per-provider setup steps and device requirements are not recorded in PRISM. Check the original guides.

HID Bluetooth (Apple & Google) · HID Wallet (Apple) · Swiftconnect (Apple)

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Package handling is available to Security Managers, Building Managers and Building Admins from the dashboard. Check-in requires recipient, barcode (scanned or typed), carrier and type; notes are optional.

Packages

Documented behavior: Check-in automatically notifies the recipient by email, and by SMS if their profile has a phone number. Check-out is done by scanning or picking from a list; if the property enables signature collection, staff must capture a signature before the status changes to Picked Up with a timestamp.

Packages

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: A Standard survey's results are visible only to the internal team. A Community survey lets other app users see results, and respondents can opt in to share answers with their name. A survey can also be added as its own tile on the app home screen.

Surveys: Creating a Survey

Documented behavior: Surveys are distributed by linking them from a mobile highlight's action button or from a push-notification announcement; the sending article describes no other distribution or audience-targeting step inside the survey itself.

Surveys: Sending A Survey

Documented behavior: Each survey has its own live response table that can be sorted, filtered and downloaded. Questions use 10+ types with a short label that becomes the column name in the response table, and each question can be marked required.

Surveys: Results · Surveys: Creating a Survey

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: A waiver can stand alone in the app or be attached to a highlight or event. Name, email and submission date are captured automatically, so custom questions (10+ types, optional required flag) are only needed for anything else. The setup also includes an Openpath configuration section.

Waivers: Overview · Waivers: Creating Custom Questions

Documented behavior: Signature title and electronic signature consent language are pre-filled and editable; that section is required for a digitally signed waiver. Signers get an email confirmation, and extra recipients can be added as comma-separated addresses.

Waivers: Signature Settings · Waivers: Visibility & Notifications

Exception / edge case: Deleting a waiver also deletes its responses, so Cove recommends hiding it instead. Responses can be sorted, filtered by each custom question and downloaded as CSV, and staff can add a manual entry with a photo of a paper copy.

Waivers: Visibility & Notifications · Waivers: Responses

Limitation / verification point: The Insights guide describes configurable Boards and Cards over supported datasets. Inspect available filters and groupings for the buyer’s actual question; the existence of reporting does not establish every cross-event or tenant-level analysis.

Insights Dashboard

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Limitation / verification point: Cove's Activity Log is a manually written record of building events such as front-desk observations or minor incidents. The article does not describe an automatic audit trail of changes made in Cove, so do not treat it as a system change history.

Activity Log

Permissions: Building Admins configure the Activity Log. Reservation, Security, Engineering and Building Managers, Building Engineers and Building Admins can add and view entries. If the module is missing, Cove's Customer Success team must enable it.

Activity Log

Documented behavior: An entry needs a date and time (defaults to now and cannot be in the future) and notes; tenant or household and location are optional. Only the author can edit an entry. The table can be searched and filtered and exports to CSV with the current filters and visible columns.

Activity Log

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Displays are web pages: open display.cove.is/activate full screen on a smart TV browser or a signage device such as Airtame, then enter the shown activation code under Engage > Display Management. Smart TVs suit a few screens; Airtame suits campuses that need remote management.

Displays

Documented behavior: Each display shows one of three layouts: full-screen highlights and events only; highlights with a weather widget; or highlights with a tenant directory filtered by building, which needs buildings, floors and suites set up first. Without a directory, weather is shown instead.

Displays

Limitation / verification point: Cove displays do not play MP4 or streamed video, embedded web content or live widgets; content should be static images and text. Pages adapt to portrait screens with the same URL, but some TVs or Airtame devices must be switched to portrait manually.

Vertical Displays

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: COI AI Review takes several ACORD 25 PDFs at once, one tenant or vendor per file and up to 35 MB each. Extraction can take several minutes and the review table does not refresh itself. Documents that are not ACORD 25 are still processed but flagged for review.

COI Extraction: AI Review

Documented behavior: An admin approves every extraction in two views, a summary and then the PDF side by side, and can override the certificate holder and additional insured matches. New carrier policy names need a one-time mapping that is reused for that property only; custom policy questions are never extracted.

COI Extraction: AI Review

Limitation / verification point: Cove's FAQ says CoveAI uses enterprise model APIs plus Cove's own infrastructure, sends only the data a request needs, and that AI subprocessors do not train on client data. Default instructions set a professional tone and discourage invented facts; users can adjust tone per feature.

CoveAI FAQ

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Visitt has four roles: Global Admin (all properties, fixed permissions), Property Admin (users and settings for assigned properties), Manager (all work orders and inspections, no settings or user management) and Team Member (only assigned work). Only Global Admins change roles, with a comparison prompt and a permission log.

How to Add Users to Your Property · How to Change User Permissions

Documented behavior: Admins add existing users or invite new ones, who get a one-time code by email or SMS and can log in immediately. Access can be per region or property, global (all current and future properties), or via Property Groups, which grant and remove access automatically as properties join or leave a group.

How to Add Users to Your Property · Assign User Access by Property Group

Exception / edge case: Deactivating a user blocks login across all properties and keeps their data, but drops their work orders, inspections and automations without offering reassignment. To hand work over, first unassign them from each property, which lets an admin transfer open responsibilities to another user there.

How to Deactivate or Remove Users from Properties · How to Transfer Responsibilities from One User to Another

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Permissions: Only Global Admins see the account-wide Buildings and Properties pages. Buildings lists each building's occupied and total leasable spaces, floors, spaces, area and address, and can add buildings and export; existing buildings are edited inside the property. Properties sets each property's asset type and region.

Global Settings: Buildings · Manage properties in Global Settings

Exception / edge case: Moving a property to another region takes effect immediately and can change which users have access when access is region-based; changing asset type affects only classification and reporting. A building without an address gets no regional holiday logic.

Manage properties in Global Settings · Global Settings: Buildings

Documented behavior: With Primary Properties switched on by a Global Admin, only users marked primary for a property get its routine notifications and appear first when assigning work; others keep access and are notified only when assigned, mentioned, subscribed or delegated. Admins cannot change their own primary properties.

Set Up Primary Properties

Documented behavior: My Property shows a building tree from floor to space, subspace and equipment, with search and filters for equipment or leasable spaces, plus a section for items with no floor. Building addresses appear in work order forms and filters. Only Visitt technical support can remove a building.

My Property: Page Overview

Documented behavior: Use My Property and the Spaces tab to create either a shared/operational building space or a leasable space. A space must be marked leasable to be available as leasable space on tenant records. Its detail view links equipment, work orders, inspection history and QR context.

My Property - Spaces

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Global Admins manage work order categories under Settings > Account > Categories, either one list for all properties or scoped by asset type. Four switches decide whether property admins may add or hide main categories and subcategories; all are on by default, and turning all off locks properties to the global list.

Global Categories

Exception / edge case: Hiding a category affects one property and keeps history. Removing one at account level cannot be undone, takes it off linked items and stops integration syncing, with an option to keep it locally where already used. When admins add a local category, Visitt suggests similar existing ones to avoid duplicates.

Global Categories

Documented behavior: Categories and subcategories organize work orders and inspections and sync to Visitt+, where tenants choose one when submitting a request. Each category appears only on the properties it is assigned to.

How to Manage Your Categories

Permissions: Only Global Admins create inspection and broadcast templates shared across all properties; others get an Unauthorized error. An inspection saved as a template drops its spaces, equipment and assigned users, which must be set at each property.

How to Create and Manage Visitt Templates

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Per the Hebrew guide, a new work order takes a description from which Visitt AI suggests a category, a building, a location searchable by floor, space, equipment or tenant (which suggests related contacts), an assignee, priority from low to critical and a due date, plus optional template, checklist, recurrence and photo, video or PDF files.

כיצד ליצור קריאת עבודה: תהליך חדש ומשופר (Hebrew)

Exception / edge case: With work order approval enabled, new orders start as Awaiting Accept. Changing status accepts automatically; declining needs a reason and another assignee; reopening a completed or canceled order auto-accepts it for the reopener. Checklists, which record who ticked each item, are hidden from tenants.

כיצד ליצור קריאת עבודה: תהליך חדש ומשופר (Hebrew) · Work Order Acceptance

Documented behavior: Assignees, the creator, chat participants, people mentioned or notified by escalation rules, and self-subscribers receive push notifications for messages, status, due date and overdue changes. Assignees cannot unsubscribe, and team members can manage only their own subscription.

Work Order Subscribers

Documented behavior: Per the Hebrew overview, the work orders page has Open, All, a calendar (web only), automations that assign users and time frames by category or unseen time, and templates. CSV export lets users choose fields and is limited to 5,000 work orders per export.

מבט כולל על עמוד קריאות (Hebrew)

Permissions: Only Admins can delete work orders, singly or in bulk, and deletion is permanent and unrecoverable. Non-admins do not see the Delete option.

How to Delete Work Orders

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Per the Hebrew guides, managers can view and edit everyone's work orders, while field staff see their open tasks on the main screen and all tickets on the Tickets page. Status, location, due date and assignees can be changed by tapping them, and status can be changed straight from the list.

איך לטפל בקריאות שירות: מדריך למנהלים ואנשי שטח (Hebrew) · ניהול וביצוע קריאות שבר (אנשי שטח) (Hebrew)

Exception / edge case: Files or photos added with the attach button are attached to the work order itself, not the chat message, even in the internal team chat, and become visible to all teams on the ticket. Staff should check a file is suitable before uploading.

ניהול וביצוע קריאות שבר (אנשי שטח) (Hebrew) · איך לטפל בקריאות שירות: מדריך למנהלים ואנשי שטח (Hebrew)

Documented behavior: Each work order has separate team and tenant chats, and Visitt AI can rephrase messages to tenants. In the mobile app, My Work can group tickets by status or due date, and saved column layouts persist between visits.

ניהול וביצוע קריאות שבר (אנשי שטח) (Hebrew)

Exception / edge case: When staff cannot see work orders, the usual cause is assignment or automation changes by property management. Device fixes are clearing site data from the profile, then logging out and back in, before escalating to the property admin or Visitt support.

How can I troubleshoot work order visibility issues in the Visitt app?

Documented behavior: In Work Orders, an administrator defines an automation trigger, priority, building and category conditions, then an action. The documented selection order favors more-specific matches, beginning with subcategory and category.

How to Set Work Order Automations

Limitation / verification point: New rules do not apply retroactively. An automation does not overwrite a field that already has a value; that also matters for recurring requests created with an assignee. Distinguish rule configuration from AI classification.

How to Set Work Order Automations

Documented behavior: Global admins create account-level on-call schedules, select properties, set a rotation and arrange primary and backup tiers. During off-hours, scheduled people appear prominently in the work-order assignee list. This alone does not establish automatic assignment.

Set up and manage on-call schedules

Documented behavior: A scheduled user can arrange coverage for all or part of a shift, choose a replacement from the same schedule and record a reason. The change takes effect immediately and notifies the replacement; the guide also describes cancelling that cover.

Set up and manage on-call schedules

Documented behavior: Add a location-linked QR Check section while defining inspection tasks. Download and place that location’s code on site. The documented task requires its scan before completion; scanning a location code can also expose relevant active inspection tasks or location details.

Require On-Site QR Code Scan Before Task Completion

Limitation / verification point: The Hebrew guide permits admins, and managers given permission, to reopen eligible missed closed tasks. It excludes daily and hourly tasks. A reopened task stays open for seven days; a reason for late completion is requested when the task is finished.

השלמת משימות שפוספסו

Documented behavior: Add a billable item or a new charge to an open request and request tenant approval when needed. After the work is completed, a manager reviews and verifies the charges in Billing. The guide says verified charges and work-order status cannot then be edited.

Billing Management

Documented behavior: With Yardi enabled, Verify Only retains a verified charge without queueing it; Verify for Sync puts it in Awaiting Sync. Before synchronization, charges can be moved into or out of the queue. Without Yardi, verification is the final in-app billing state and charges can be exported.

Billing Management

Limitation / verification point: The Accounting Sync Panel exposes queued items and synchronization errors. Manual sync supports a target post month. The guide says success/failure notifications are unavailable, so the panel must be checked; this does not prove downstream ledger posting.

Billing Management

Documented behavior: A global vendor is one account-level record linked to properties. Global admins can create, upgrade or merge records and apply a Verified badge. Property-admin creation rights are configurable. Merging preserves property-specific contacts, COIs and work orders while combining the shared vendor identity.

Manage Global Vendors Across Your Portfolio

Limitation / verification point: COI tracking remains property-specific even for a global vendor. A global verification badge should not be read as proof that every property’s insurance requirements are satisfied.

Manage Global Vendors Across Your Portfolio

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Tenant requirements are set once per property and inherited, or customized per tenant; vendors get requirements through policy categories such as high risk assigned on the vendor record. Requirements can be AI-extracted from a lease or insurance PDF (best under two pages; PNG and JPEG unsupported), with extracted fields labelled.

Set up and validate tenant COI requirements · אישורים ביטוחיים לדיירים ולקבלני משנה (Hebrew)

Documented behavior: Per the Hebrew guide, an uploaded COI is compared field by field, required against received: green when met or exceeded, orange on a mismatch. Statuses are Compliant, Non-compliant (expired or failed the AI check) and Missing; compliant COIs expiring within 30 days are highlighted on the Status page.

אישורים ביטוחיים לדיירים ולקבלני משנה (Hebrew)

Exception / edge case: A COI owner can still mark a mismatched COI Compliant if the difference is acceptable. Without requirements, no automatic validation runs. Tenants set to not track compliance disappear from the COI list and report, and requirement changes cannot be undone; revalidating sets the COI to Pending.

Set up and validate tenant COI requirements · אישורים ביטוחיים לדיירים ולקבלני משנה (Hebrew)

Documented behavior: COI owners set reminders before and after expiry; one is always sent on the expiry day. Reminders go to the owners and the tenant or vendor renewal contact, who can reply by email with the new certificate, which reaches the owners for upload. Reminder emails can be edited and carry a sample or requirements file.

אישורים ביטוחיים לדיירים ולקבלני משנה (Hebrew)

Permissions: Admins and Managers who are COI owners set requirements and validate certificates; view-only Managers cannot. Global Admins get a portfolio COI report filterable by tenant or vendor, with compliant, non-compliant and missing counts, exportable to CSV or PDF.

Set up and validate tenant COI requirements · אישורים ביטוחיים לדיירים ולקבלני משנה (Hebrew)

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Documents live under Documents & COI with a property, optional tenant or vendor link, tags, files (images or PDFs), start and expiry dates (6 months, 1 year or custom) and reminders. Expired documents show red and those close to expiry orange, and documents can be exported as CSV or as their files.

Documents in Visitt

Documented behavior: Adding a new file or validity period automatically moves the previous current version to a History tab, even if it is still valid, giving an audit trail of past versions without extra steps.

Documents in Visitt

Permissions: Only Admins can delete documents, one at a time or in bulk; other users must ask an Admin to change their user type. Expiry reminders depend on the user's notification settings being enabled.

Documents in Visitt

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: A tenant card shows an overview with contacts, open requests and satisfaction, plus contacts, authorized spaces, documents with expiry reminders, and billing fields (tenant code, company, billing contact and address) printed on that tenant's work order invoice PDFs.

Manage Your Tenants in Visitt

Exception / edge case: Per the Hebrew guide, a tenant needs at least one leased or authorized space before its contacts can submit requests. Leased spaces must first be marked rentable on My Property, except when assigned while creating a tenant from the table. Shared spaces for all tenants are set in the tenant app admin.

הוספת אתרים לדיירים (Hebrew)

Permissions: Only Admins or Managers with tenant management permission archive or restore contacts. Archiving keeps the contact's data but blocks login to the tenant app; restoring uses the Archive toggle and the Restore column. Contacts are invited by a link to download Visitt+.

How to Archive and Restore Contacts · Manage Your Tenants in Visitt

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Settings > Property > Tenant App sets brand colors, logo, building cover image, an optional satisfaction survey after completed work orders, tenant request categories with icons and custom fields, and common areas open to all tenants, with a live preview. The logo also appears on every tenant email notification.

Managing Your Tenant App

Documented behavior: Visitt AI smart category can be switched on so tenants only describe the problem and the AI chooses the request category for them.

Managing Your Tenant App

Permissions: Content pages are open to Admins by default; Managers need an Admin to grant access. Pages are custom app pages or document pages, with rich text, sub-pages, drafts, publish and unpublish, and desktop and mobile previews; drafts are visible only to the property team.

Content: Create and Manage Tenant App Pages · Content: Create and Manage Tenant App Pages

Exception / edge case: Pages placed in Highlights currently appear in reverse order, so the last page added shows first in the tenant app. Other pages sit under the app's Content tab (an older version of the article calls it More).

Content: Create and Manage Tenant App Pages

Documented behavior: The property team must first add the tenant user. Login uses an emailed or texted six-digit code. The current guide places property switching in the avatar/settings area and broadcasts in the inbox; notification channels depend on property configuration.

Getting Started with Visitt+: A Guide for Tenants

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: In the Visitt+ tenant app, requests start from the plus button (also used for visitors and amenity bookings) with a category, description and optional attachment; the Hebrew guide mentions files, photos or video. Visitt routes each request using the property's assignment rules.

Visitt+ Work Orders: Create and track requests · איך ליצור קריאות עבודה ב +Visitt (Hebrew)

Documented behavior: Tenants see Open and Closed requests and can message the property team in a chat beside each request. Visitt support does not give out property managers' contact details, so tenants are directed to submit a request instead.

Visitt+ Work Orders: Create and track requests

Exception / edge case: A request missing from Closed may still be open, or may belong to another property: tenants linked to several properties must switch property from the settings panel under their initials to see it.

Visitt+ Work Orders: Create and track requests

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Each amenity has a cover image, maximum occupancy, location, an assigned overseer, time-slot length, cost per booking and opening days and hours. The price shows in the tenant app only if Billable is ticked for each day. Optional required booking questions collect extra details such as guest numbers.

Visitt Amenities for Property Managers

Documented behavior: Rules can set how far ahead tenants may book, cleaning buffers blocked before and after each booking, a maximum booking length, and links between amenities that share one physical space so they cannot be double-booked.

Visitt Amenities for Property Managers

Exception / edge case: Every amenity booking creates a work order that staff must complete, both as a reminder to approve or reject and for setup. Staff can approve, reject with a reason, cancel, edit, or book manually for a tenant; statuses are Approved, Canceled, Inquiry and Pending.

Visitt Amenities for Property Managers

Documented behavior: Tenants book in Visitt+ from the plus button with amenity, date, time and notes, which notifies the property manager. They see the booking status, can chat with the building team about it, and can edit or cancel it from Details.

Amenities (Visitt+)

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Staff add a visitor with a host who may or may not be a contact, first and last name, optional email, and a single day (all day or timed) or multi-day range. The visitor receives an email or SMS with a unique QR code for entry, and Cancel Permission revokes access immediately.

Managing Visitors: A Complete Guide

Documented behavior: Tenants invite visitors in Visitt+ (plus button on mobile, Visitor Invite on desktop) and see upcoming visitors on their home screen. The staff table shows the inviting contact and can be filtered by valid or expired access, building and tenant, with check-in and check-out times.

Visitors Overview · Managing Visitors: A Complete Guide

Exception / edge case: Watchlist matches (exact names, manual variants and, with Visitt AI on, AI variants; beta) raise a red Possible Watchlist Match alert before arrival with the reason and action instructions. Nothing blocks check-in automatically; staff contact the tenant, allow, deny or clear the alert.

Visitors Watchlist

Permissions: Admins add watchlist entries for any tenant. Tenant primary contacts can manage their own entries in Visitt+ only if the property enables it, and only in a web browser, not the mobile app or mobile web view. Entries record name variants, an optional photo, instructions and who added them.

Visitors Watchlist

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Staff log a package with the recipient contact, a scanned or typed barcode or QR code, courier and notes the tenant can see; saving notifies the contact automatically. Each package shows when it was created and by whom.

Managing Packages

Documented behavior: Marking a package picked up prompts the tenant for an e-signature to confirm collection. Tenants choose in the app whether package notifications arrive by email, SMS or push. The help article dates from August 2024.

Managing Packages

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Broadcasts must be enabled for the property. Staff target recipients by building, tenant, contact or a saved Broadcast Group, with a live recipient count, and must choose at least one channel: email, SMS or push. Messages can use templates, attachments, branding presets and AI enhancement where available.

How to Use Visitt's Broadcast Messaging

Documented behavior: The composer previews email, push and in-app views before sending, sets the sender name and notification language, and allows replies when a reply-to email is configured. Broadcasts send immediately with Send Now; the article describes no scheduling option.

How to Use Visitt's Broadcast Messaging

Documented behavior: Tenants read broadcasts in the Visitt+ Inbox and are alerted by push, email or SMS depending on property settings. Tenants can log in only after the property team adds them, using a six-digit code sent to their email or phone.

Getting Started with Visitt+: A Guide for Tenants

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: The Status page opens on a daily view with tenant Visitt+ reviews linked to their work orders, a Metrics view of the last 30 days and a Portfolio view per property. Reports cover work orders (overview, SLA, AI Discovery of recurring issues), inspections, tenants and amenities, and export to PDF.

Status Page Explained · How to View and Export Reports

Documented behavior: Per the Hebrew guide, the operational score combines on-time work orders, preventive maintenance and daily rounds over 30 days, document validity, and 90-day tenant ratings. It appears only when at least 3 of the 5 areas are used and is capped by coverage (3 areas means at most 60%). Only Admins and Managers see it.

עמוד סטאטוס - ציון תפעולי (Hebrew)

Documented behavior: Views save filters over work orders, inspections or both, for chosen or all assigned properties, as personal or shared with named users in the organization. Each viewer sees only data they have access to; only the creator or an admin can edit or delete a view, and view data can be exported.

Create and Manage Views

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Per an August 2024 article, Visitt AI flags new work orders that resemble earlier ones from the same reporter, signalling duplicates or recurring problems, and collects these in the Work Orders Discovery report. It also generates keyword titles for new work orders from their descriptions.

Visitt AI Capabilities

Documented behavior: Staff can press an AI button under any chat box to get several rephrased versions of a message for colleagues or tenants. AI Smart Categories, switched on in the tenant app admin, lets tenants type a request and have its category assigned automatically.

Visitt AI Capabilities · ניהול וביצוע קריאות שבר (אנשי שטח) (Hebrew)

Documented behavior: Tenant COI requirements can be extracted by AI from an uploaded PDF (best under two pages) or entered manually, once per property or per tenant. COIs are then checked automatically against the saved requirements, but a person still marks each COI Compliant.

Set up and validate tenant COI requirements

Permissions: Admins and Managers who are COI owners can set requirements and validate COIs; view-only Managers cannot. Changing requirements prompts revalidation, which sets the COI to Pending for manual review, and requirement changes cannot be undone.

Set up and validate tenant COI requirements

AI-extracted, not reviewed: Claude extracted the notes below from the cited help articles as captured on September 28, 2026. No person has reviewed them; check the source before relying on one.

Documented behavior: Staff log in with a one-time code, a password or SSO, as chosen by their organization's Admin or IT team; when SSO is configured it is the only option. Visitt Support cannot change login methods or SSO settings, and a 'can't find your account' error usually means the user was never added.

How to Log In to Your Account

Documented behavior: From the name menu, staff set availability (Active, Away or scheduled hours), schedule Out of Office with a backup who receives their work and notifications, change the interface language, clear site data or invite users. Notification preferences are set per feature for email, SMS and push.

Configuring Profile Settings

Permissions: Admins have full access, Managers most features with some actions needing Admin permission, and Team Members only what an Admin enables. Only Admins manage other users' details, role, properties and permissions; whether staff can add or remove themselves from properties depends on their role.

Configuring Profile Settings · How to Manage a User's Profile