Users, Roles & Permissions
How access works across Equipt, Landscapt, crew logins, and the client portal — and why they aren't all the same system.
On this page
Two separate role systems
Equipt/PO and Landscapt/CRM access are controlled by two independent mechanisms, not one unified role model:
- The organization role — one role on every user's login: Admin, Manager, Purchaser, Staff, Viewer, Requestor, or Crew. This is the role you pick when inviting someone from Settings → Users, and it's what controls Equipt (CMMS) and purchasing access.
- CRM custom roles — a completely separate, org-defined permission system for Landscapt, managed at Settings → Landscapt Settings → Roles. Each role is a named set of on/off switches (over a hundred of them — client access, scheduling, accounting, reports, and more), closer to Service Autopilot's permission model than to the seven fixed organization roles.
The seven organization roles
These are the only organization roles there are. Every staff login has exactly one.
| Role | What it means |
|---|---|
| Admin | Full access to everything — all modules, all records, settings, approval flows, and user management. |
| Manager | Full operational access across purchasing and maintenance — everything except organization settings and user management. |
| Purchaser | Manages the full procurement lifecycle from requisition to receiving. Read-only on work orders. Can submit maintenance requests and edit or delete their own while they're still Open, but can't review or convert requests. |
| Staff | Standard Equipt access — creates and manages work orders (not limited to ones assigned to them), and can initiate procurement for parts. |
| Viewer | Read-only in Equipt, including costs and prices. No create, edit, delete, or approve access there. Landscapt access follows their Landscapt role. |
| Requestor | Submits maintenance requests and draft purchase requisitions only. Can edit or delete their own maintenance request (title, description, priority, asset/vehicle) only while it's still Open — once it's being reviewed it's locked. Can't approve, review or convert anything, and has no access to assets, vendors, or inventory. Sees no Equipt costs: work-order parts, labor and vendor charges, part costs, purchase orders and receiving are hidden. |
| Crew | A shared login for a field crew team (e.g. MAINT1, ENHANCE1), not an individual person — confined to the crew field surface, not the full dashboard. In Equipt it can only file repair requests (and see the asset and vehicle names to pick from). |
Role permission matrix
A snapshot of what each organization role can do, drawn from the role descriptions shown in Settings → Users → Roles.
| Role | Manage users | Approve req./POs | Edit org settings | Equipt/PO access | Landscapt/CRM access | Client portal access |
|---|---|---|---|---|---|---|
| Admin | Yes | Yes | Yes | Full | Full (bypasses CRM role permissions entirely) | Automatic |
| Manager | No | Yes (within limit) | No | Full | None by default — needs a CRM role assigned separately | N/A |
| Purchaser | No | No | No | Requisitions/POs/receiving/vendors full; work orders read-only | None by default | N/A |
| Staff | No | No | No | Work orders, PM, parts, meters full; can create requisitions/POs for parts | None by default | N/A |
| Viewer | No | No | No | Read-only | None by default | N/A |
| Requestor | No | No | No | Maintenance requests (own, editable while Open) + draft requisitions only; no costs | None by default | N/A |
| Crew | No | No | No | Repair requests only (own requests; asset/vehicle names) | None — crew app only | N/A |
"None by default" for CRM access means the organization role alone doesn't grant it — an admin has to link the user to an employee record with a Landscapt role under Team → Employees. Client portal accounts are a different login entirely — see the Client Portal guide.
Landscapt/CRM custom roles
Landscapt access is governed by Landscapt roles — roles you build yourself at Settings → Landscapt Settings → Roles, not the seven fixed organization roles above. Each role is a list of permissions (Add Client, Add/Modify Invoices, Dispatch Board, and well over a hundred others across Home, CRM, Scheduling, Accounting, and Mobile) that you switch on or off per role.
Starter roles. Every new company starts with nine ready-made roles (Owner, Operations Manager, Office Admin, Accounting, Sales / Account Mgr, Scheduler, Customer Support Rep, Crew Leader, Fertilizer Tech) that you can edit or copy. Owner and Operations Manager have every permission, including warranties, commissions and the payroll report; Office Admin also gets warranties and the payroll report, and Sales / Account Mgr gets warranties and “View My Own Commissions”. When a new permission is added to Landscapt, the starter roles that should have it get it too; a box you unticked on a role stays unticked.
To give someone CRM access, two things have to both be true:
- They have an employee record (Team → Employees) linked to their login. On the employee record, pick the login from the Select a user to link… dropdown — it lists active users who aren't already linked to another employee, and once linked it shows their name and email.
- That employee record has an active Landscapt Role — the role that defines what they can see and do inside Landscapt.
The employee record must be in the same organization as the login. A login can only be linked to an employee record (or a crew's Linked Login) in its own organization; linking a login from another organization, or a client portal login, is refused with "That login does not belong to this organization".
Without both, a user with a perfectly valid organization role (say, Manager) is blocked from Landscapt entirely — Landscapt checks for a Landscapt role on their employee record, not their organization role. The Landscapt tile on their Home screen reflects this too: it only appears once both conditions above are met, so an unlinked user simply doesn't see a tile that would otherwise dead-end in a "not linked" screen.
Money actions are checked inside the database, per permission. Having CRM access is not enough to move money: refunding or voiding a payment needs the refund/void or delete-payment permission, recording or editing a payment or credit needs Add/Modify Payments or Credits, applying money or credit to an invoice needs the payment or credit permission, and merging invoices, invoicing a project milestone and reconciling an invoice's payments need Add/Modify Invoices (reconcile accepts the payment permissions too). The system checks the same permissions the buttons use, so a role without them is refused even if it tries the action another way.
Cancelling jobs and bulk-editing clients are enforced the same way. Setting a job to Cancelled needs the Cancel Job permission, and changing a field (account type, source, priority, email opt-in, do-not-market, or status to Inactive) on more than one client at a time needs Bulk Edit. Editing one client at a time only needs the normal client edit permission. A role without the permission sees a "You do not have permission" error rather than a silent failure.
Creating and changing records is checked inside the database too. These permissions are enforced on every save, not just by hiding buttons:
- Invoices and invoice lines need Add/Modify Invoices. Without it, a role can still print or QuickBooks-sync an invoice it can see (which locks it and moves a draft to Printed), but not unlock it or change it. Marking an invoice Sent, or emailing it, needs Email Invoices. Generate Snow Invoices and Create Invoices from Contracts let a role create the draft invoices those screens generate. Completing a visit, or a one-time job, still creates its automatic invoice for anyone allowed to complete it. Once a job has been invoiced, changing its service rates, quantities or taxable flag needs Add/Modify Invoices.
- Job materials on an invoice: anyone who can work a job's Products list can take a material off its invoice (Remove from Invoice, Used — do not Invoice, Not Used) while that invoice is still an unlocked draft; the invoice line and totals update with it. Once the invoice has been printed or sent, that needs Add/Modify Invoices, and a locked invoice must be unlocked first.
- Estimates (and their line items, sub-items, equipment, direct costs, photos and payment-plan milestones) need Add Estimate to create and Edit Estimate to change or delete. Add Estimate alone also covers finishing a new estimate you created that hasn't been sent. Send Estimate alone can mark an estimate sent (and nothing else), and Add Job alone can mark an open estimate accepted when converting it to a job.
- Project billing milestones need Add/Modify Projects or Add/Modify Invoices. Once an estimate is converted to a project, its milestones belong to the project: they show as read-only on the estimate for a role that can edit estimates but not projects. Converting the estimate (Add Job) carries them onto the project. Invoicing a milestone, or changing whether it is invoiced, needs Add/Modify Invoices on either screen.
- Contracts (and their notes) need Add, Edit or Delete Contract for each action; Create Invoices from Contracts may only record the billing dates it stamps.
- New jobs need Add Job (a project also allows Add/Modify Projects).
- Tickets need View/Modify Tickets to edit, close, reassign, delete or restore. A crew login can still edit a ticket it created itself (for example a field upsell suggestion).
- Campaigns need Add Campaign to be created, Send/Launch Campaign to be scheduled or sent (including Mark Scheduled), Edit Campaign for other changes and Delete Campaign to delete.
- Services need Add, Edit or Delete Service (or the Scheduling settings permission). Settings → Accounting needs the Accounting settings permission (or CRM settings). Company settings also covers the tax rate, ACH and card fee, but not invoice or estimate numbering.
- Automations need Create/Modify Automation; Stop Automation alone can only switch one on or off. Document templates and packages need their Add, Edit or Delete permission. Teams need Teams; the Dispatch Board permission can still add an employee to a crew's roster and set a crew's default equipment.
- Schedules (the recurring-schedule templates) need the Scheduling settings permission to edit, rename, switch off, delete or reschedule; without it the Schedules page and sidebar item are hidden. Add Job can still create a new schedule from a job's Recurring Schedule picker.
Changing the schedule needs a scheduling permission. Scheduling a new visit, moving it to another day, changing its crew, dispatching, skipping, cancelling, completing or deleting it, bulk-updating visits, generating visits and changing a job's materials need one of: Dispatch Board, Waiting List, Manage Snow Dispatch or Add Job (Settings → Schedules re-generating visits uses the Scheduling settings permission, and a project-type job also accepts Add/Modify Projects). View Jobs alone is view-only — a role with just View Jobs can open jobs and their visits and add notes, but the Complete, Schedule Visit, Generate Visits and per-visit dispatch, skip and delete actions are hidden, and the database refuses those changes. Cancelling a job (Cancel Job) or a contract (Edit / Delete Contract) still cancels that job's untouched visits. Crew app logins are not affected — the crew app has its own rules.
A visit's price and quantity need Change Visit Price & Quantity. The Qty and Rate on a visit are what the visit bills when it's completed, so changing them — on the Dispatch Board's visit sheet or anywhere else — needs the Change Visit Price & Quantity box (Scheduling Access). It's separate from Add/Modify Invoices, so a scheduler can re-price a visit without getting access to invoices. Without it those two fields are locked; everything else on the visit sheet still saves. Notes, invoice descriptions, hours and crew size on a visit stay open to every CRM role. Giving an invoice its number (which happens when it is printed, emailed or saved) is open to anyone who can see the invoice.
Client notes, stored card and balance are protected on write. Changing a client's Office Notes needs View Notes. Changing the stored payment method, or turning autopay on, needs View Credit Card #'s plus Add/Modify Payments. Changing a balance directly needs View Balance plus Add/Modify Credits (balances recalculated from invoices and payments are unaffected). Turning autopay off is always allowed. Still hide-only: View Notes, View Credit Card #'s, View Balance, View Billing and Export Lists control what the screen shows and offers, but they don't withhold the data itself from that login, and an export contains whatever the screen has already loaded.
Report permissions live on the role editor's Reports tab and work in two layers, both checked by the system itself, not just by hiding buttons:
- View Report Center (Home > Report Access) is the front door. It is required to open the Report Center and to run or save a custom analysis, open a saved report, view a Custom Dashboard, or use the Graphics Library. Manage Report Center additionally allows building those and editing the KPI Scorecard, and is also what lets someone create or change dashboards, custom reports and scheduled report emails. The database itself refuses those writes without it, so a view-only role can't do them any other way.
- View & Edit Payroll Report (Home > Report Access) unlocks the Payroll tab in the Report Center, where each person's Start Day / End Day hours are reviewed, corrected and exported. Admins always have it; the default Owner, Operations Manager and Office Admin roles have it. An organization role of Manager alone does not grant it. It also lets someone correct crew punches in the dispatch board's Edit Job Times and choose whether a stop's pause is paid — the same things the Dispatch Board permission allows. Nobody else can change crew punches.
- Show Wage Burden (Payroll Access) is what shows a crew member's labor burden rate on Team → Crews and lets someone change it, and it shows the labor rate and labor cost in the Timesheet reports and the cost column of Resource Time Utilization. Without it those numbers are blank or hidden — and crew logins never see them. Job Costing totals are unaffected.
- Individual report permissions under CRM Reports, Scheduling Reports, and Accounting Reports each unlock one pre-built report by name (Client Balance, Job Cost Summary, A/R Aging Report, …). The same permissions also control the datasets behind custom analyses and dashboard panels, so a role that can't see a payroll or accounting report can't rebuild it ad hoc either: Employees needs Employee Directory; Timesheets needs Job Hours Summary or Employee Directory; Crew Drive Time needs Job Hours Summary; Job Visits and Job Services need Job Costing, Job Cost Summary, Cost of Goods Sold Report, or Job Hours Summary; Projects — WIP Schedule needs Job Costing or Job Cost Summary; Invoices and Invoice Line Items need Invoiced Income by Client, Invoices with Balances, or A/R Aging Report; Contracts needs Client Contracts, Package Summary Report, or one of those three; Payments needs Payment Audit Summary or one of those three; Estimates and Estimate Line Items need View Estimates, Estimates by Stage, or Won Estimates by Service; Audit Log needs Audit Log or Security & Access Audit. A dashboard panel the user can't query shows "You don't have permission to view this panel" rather than failing the whole dashboard.
- Dashboard Access (Home > Dashboard Access in the role editor) has one View permission per built-in dashboard — Equipt Dashboard, My Day, Reports Dashboard, KPI Scorecard, Driver Safety Scores, Company Report, Social Media, Custom Dashboards, Job Costing, Estimate Builder, and Calculators. A role without one doesn't see that dashboard in the Dashboards sidebar or overview, and opening its web address directly is blocked. Admins always see everything. A login with no Landscapt role sees none of these dashboards, with one exception: Equipt-only staff (a shop mechanic, say) still get the Equipt Dashboard and Driver Safety Scores based on their organization role.
Inviting a new user
- Go to Settings → Users. Only Admins see the Invite User and Create Crew Account buttons.
- Click Invite User, enter their name, email, and pick one of the organization roles.
- For anyone who isn't an Admin or Crew, optionally pick a Landscapt role. Landscapt access comes from a Landscapt role on an employee record, not from the login role, so choosing one adds them to your employee list and links the two for you. Leave it blank and they can sign in but see a "No Landscapt access yet" screen until an admin links them under Team → Employees. The invite email names your company.
- They receive an email invitation and set their own password on first login. If the email is already registered elsewhere in the system, a password-reset link is sent instead so they land on the same set-password screen. If the email belongs to a different type of account, such as a client portal login, or to a user in another organization, the invite is refused with a message; use a different email. If that other organization is a free trial the person started on their own that ended without a subscription, the message says so — contact support to move their login to your team. Inviting someone who is already an active member of your team is refused too ("already an active member") — change their role in the table instead. If the invitee's employee record already has a different Landscapt role, that role is kept and the invite says so; change it under Team → Employees.
- Invite links are single-use and expire for security. If a link no longer works, an Admin can resend the invite. Opening an invite link again after the account is set up says "You're already set up" with a link to sign in.
- An Admin can resend a pending invite, change a user's role, or deactivate them at any time from the same table. Deactivating revokes their login outright — it's not just a status label, it bans their account the same moment, so they can't sign in again, and a session that's already open loses access to your organization's data immediately rather than lingering until it expires. A deactivated user shows an Inactive badge and a reactivate icon in place of the trash icon; clicking it restores their login immediately, with their role and any CRM employee link untouched. A deactivated user can't be re-invited (use Reactivate instead), and a deactivated admin can't use the invite, reset-password or deactivate actions. The last active Admin can't be deactivated or changed to another role — the role change or deactivation is refused with "This is the last active admin — promote another admin first".
- Changing an Admin to another role opens a confirmation that lists the API keys they created and the apps they connected (Claude, MCP clients and other OAuth apps), with Revoke these keys and Disconnect these apps checked by default. Keys and connected apps keep working after the role change unless you revoke them there, or later under Settings → Integrations. Cancel leaves the role unchanged.
- A login and its employee record stay in sync. Deactivating a user on the Users page also deactivates their employee record under Team → Employees, and reactivating the user reactivates it. It works the other way too: deactivating (or terminating) an employee who has a login deactivates that login, and activating the employee restores the login. Because it changes the login, only an Admin can deactivate or activate an employee who has one. The deactivate dialog lists any API keys the person created, with Revoke these keys checked by default (deactivating from the Employees page revokes them as well); a key that is kept shows "Created by … (deactivated)" in the API keys list and keeps working until revoked. Report schedules the person created are paused and their own address is removed from those schedules' recipients — see Report Center → Scheduled to take one over. Marking the user's CRM employee record inactive has the same effect on permissions: a deactivated employee keeps no CRM or role permissions until reactivated. Setting an employee's Employment Status to Terminated does the same as deactivating them (and moving them back out of Terminated reactivates them). Deactivating or terminating an employee also takes them off every crew roster, so Start Day and Start Job no longer clock them in, payroll no longer carries them and the crew's headcount drops. Reactivating does not put them back on a crew; add them to a crew again (a Schedule Jobs Directly person gets their one-person crew back automatically). For a shared crew login, this only affects sign-in — to take the crew itself off the Dispatch Board, turn it off under Team → Crews instead.
A separate Create Crew Account flow (also Admin-only, same page) creates a shared login for a field crew team rather than an individual — you set a team name and a password directly, and the credentials are shown once, at creation time. If that password is lost or needs changing later, an Admin can set a new one for the account directly from the Users table. If you leave the optional Login Email blank, the login gets an auto-generated address ending in @crew.landscapt.com; those aren't real mailboxes, so they can't receive a normal password-reset email. Type a real email instead if you want one: that address gets a confirmation email, and the crew can sign in only after someone opens it and confirms the address (the success screen says so). If the confirmation email can't be sent, the account isn't created. You can't type your own @crew.landscapt.com address; leave the field blank to get one. If the generated address is already taken (two crews named "Mow 1" and "Mow-1", say), a short suffix such as -2 is added so the account is still created; the success screen shows the address to sign in with.
Crew logins are part of Landscapt, so Create Crew Account isn't available on the Equipt plan (Equipt only) — the request is refused with a note to upgrade.
Creating a crew account also creates a matching Landscapt crew and links the login to it, so the crew has a schedule the first time they sign in. If a crew with the same name already exists and has no login, that crew is linked instead. You can re-link or unlink at any time under Team → Crews → Linked Login. The password must not be a common or previously breached one — a weak password is rejected with a message asking for a longer, less guessable one.
Worked example: inviting a Staff member
An Admin invites maria@greenlawn.com as Staff. What happens immediately, and what doesn't:
- Maria gets an invite email and sets her own password.
- On first login she has full Equipt access: she can create and manage work orders (not just ones assigned to her), log labor and meter readings, submit maintenance requests, and create purchase requisitions and POs for maintenance parts.
- She cannot approve any requisition or PO — Staff isn't an eligible approver role.
- She cannot open Settings, invite other users, or change anyone's role.
- She cannot open Landscapt/CRM at all yet — inviting her as Staff only set her organization role. If she also needs CRM access (say, to see client jobs tied to a work order), an admin has to link her login to an employee record under Team → Employees and give it one of your Landscapt roles. Until that happens, every Landscapt page is blocked for her.
Crew accounts and the client portal
Two more access modes exist outside the organization-role / CRM-role pair above:
- Crew accounts — a shared login (organization role Crew) for a field team rather than a person. A crew login is confined to the crew field surface only: viewing and completing assigned jobs, submitting maintenance requests, viewing the Labor Efficiency and Driver Safety Scores dashboards, and uploading photos to job sites. It has no access to purchasing, assets, inventory, settings, or the rest of Landscapt — opening any other Landscapt page is blocked, whatever Landscapt role the crew might otherwise have.
In Equipt a crew login can only file a repair request from the field page. It can read the names of your active assets and vehicles (to pick the broken one) and see the requests it filed itself. Work orders, parts and stock, meters, PM schedules, automations, purchase orders and receiving are closed to it — it can't read them, change them or move stock, even by reading the data some other way with the crew's login. A crew's new request always starts as Open, and the crew can change it only while it is still Open, just like a Requestor.
What a crew login can change is deliberately narrow: it may update only the visits belonging to its own crew, and cannot move a visit to a different crew. Jobs and job service lines are read-only to a crew account, so a crew can never alter a service's price — pricing is only editable by staff roles with the relevant permission. Nor can a crew change the price or quantity on one of its own visits. Invoices and payments are not readable by a crew login at all. On its own visits a crew changes things only through the crew app's buttons (Start Job, breaks, Stop Job, Skip, acknowledging notes, completion notes) — it can't change a visit's date, crew, status or billing any other way — and its drive times can only be corrected by the office.
What a crew login can see about money is limited to what the crew app shows. Job prices and totals, labor and material costs, and the price and cost of materials on a job are never available to a crew login — not on screen and not by reading the data some other way with the crew's login. The one exception is each service's price on a stop, and only while Hide pricing from crew accounts is off. For the same reason, reports built on jobs and visits (revenue, rates, job costing, budget vs. actual) return no data to a crew login, even on a dashboard marked visible to crews.
The product and service catalogs are office-only as well: a crew login can't read product costs, sale prices or stock levels, or service rates and costs, anywhere — including product and service reports on a crew-visible dashboard. The crew app still shows the product names, label details and quantities a stop needs, and the services offered under Suggest work. A crew login also can't see other users' email addresses or roles, employees' HR details, or sales meetings, and it sees only its own crew's job punches.
What a crew login can see about clients is limited to the clients on its own stops. For those clients it sees the name, phone, address, gate code, property notes and contacts the stop needs, plus that client's timeline; it never sees another client's timeline, contacts or properties. A crew can add a note, a skip reason or an upsell suggestion to the timeline of a client on its stops, but it cannot edit or delete timeline entries, change a client's contacts, properties or details, or create a client. Files uploaded to a client's Files tab are not available to crew logins.
- Hiding prices from crews. Settings → Landscapt → Hide pricing from crew accounts stops service prices from being sent to crew devices at all — not merely hidden on screen. With it on, the database won't return a service price to a crew login, so prices can't be recovered from a shared tablet. Leave it off if you want crews to see each service's price on their stops. Job totals and costs are never shown to crews either way.
- Client portal accounts — an entirely different login system for Landscapt's customers (not staff), separate from everything on this page. A client portal login can only ever see that client's own account — billing, services, estimates, tickets, and documents — never any staff surface. See the Client Portal guide for how portal access is granted and what a client can do with it.
Gotchas
- Role dropdown looks editable, isn't always effective. Non-admins see the role selector as disabled, but the real protection is in the system itself — a non-admin's role change is refused however it's attempted. The disabled control is just there to avoid misleading anyone.
- Changing someone's organization role never touches their CRM role. Moving a user from Staff to Manager doesn't grant or revoke any CRM permissions — those two systems are independent, so check both when adjusting access.
- Photo Module access is a separate per-user toggle, not tied to organization role — except Admins, who always have it on, and Requestors, for whom it doesn't apply.
- A role can't be deleted while employees hold it. An employee whose Landscapt role is gone would lose Landscapt access with nothing on their record to say why, so Landscapt refuses to delete a role while employees are still assigned to it ("N employees are still assigned to this role. Reassign them to another role first."); move them to another role, then delete.
- The employee record has a third, unrelated "User Role" field — it grants nothing. Team → Employees → an employee's User Settings tab shows a User Role field with options like Admin, Manager, Staff, Purchaser, and Viewer — the same familiar names as the organization role. It is purely a display label and has no effect on access anywhere in the app. Once the employee is linked to a login, it's auto-populated from that login's real organization role and shown read-only, so it can't drift out of sync — before a login is linked, it's just a manually-set label. Don't confuse it with either the organization role or the Landscapt Role field on the same tab.
Good to know
- Deactivating a role. An inactive role grants nothing, so Landscapt asks before deactivating one and says how many active employees hold it. A role that active employees still hold can't be deactivated or deleted until they're moved to another role.
- The owner's employee record. Signing up creates an employee record for the owner with the Owner role, so they show up in sales rep and assignee pickers and in My Day's “Mine” view from day one.
- Who can change a role or linked login. On an employee record, only an admin can change the Landscapt Role or link and unlink a login. Other roles with Edit Employee see those controls disabled.
- Permission changes apply within a minute. A changed role reaches people already signed in within about a minute, or as soon as they return to the browser tab.
- Sequence approvals. Approving or rejecting a held automation message needs an admin, a manager, or Create/Modify Automation. The Approvals button is hidden from everyone else.
- Report Center data. Running reports needs View Report Center, checked in the database as well as on the page. Crew logins can still see the dashboards shared with crews.
- Invites. An invite can only give a Landscapt role that is active. Inviting someone whose old employee record is inactive (a re-hire) links and reactivates that record.
- Employee contact details. Everyone in your organization can see employee names (for assignee, crew and sales rep pickers). Home address, phone numbers, emergency contact, manager, starting address and notes show only to Admins and to roles with Edit Employee, Manage Employees or View Employee Information; Notes also show with View Resource Notes. Everyone can see their own details. Others see those fields blank on the Employees page, in the Employees report and in exports.
- Lead forms. Forms and their submissions are Landscapt data: Equipt-only logins and crew logins can't see or change them. Building or changing a form needs Edit Forms; reading submissions, marking them read and the internal test submit need View/Submit Forms; changing a submission's status or deleting it needs Edit Forms. Submissions are never permanently deleted. Public forms on your website keep working for anonymous visitors.
- Your plan decides which product you can change. On the Equipt plan you can view but not create or change Landscapt records (clients, jobs, estimates, invoices, contracts and the like); on the Starter plan the same applies to Equipt records (work orders, assets, parts, PM schedules, meters, vehicles, maintenance requests). Vendors, products, requisitions, purchase orders and projects are shared and always editable. Trial, Growth and Enterprise include both. The public API follows the same rule.
- Background work follows the plan too. On the Equipt plan, Landscapt's automatic work is paused: recurring visits aren't generated, contract invoices aren't created, past-due, card-expiry and contract-expiry reminders and scheduled campaigns aren't sent, invoices don't sync to QuickBooks, and automation steps wait. Upgrading to a plan with Landscapt resumes it from that day on — days that were skipped while paused aren't made up. On the Starter plan, Equipt's automations (meter readings, low stock, PM due, work order overdue) are paused the same way.