Customers & deployment

Everything in Caryvane belongs to a customer: agents, jobs, storage targets, connectors, users. An MSP sees its customers; a distributor sees its MSPs and their customers; nobody sees sideways. This page is the admin's tour — set up a customer, get machines enrolled, point them at storage, and know what you will be told when something goes wrong.

Customers and who can see what #

Customers shows the hierarchy: Distributor → MSP → Direct customer. Each row is a tenant with a type, a status, its agent count and its billing. New Customer creates one under you; ⋮ → Add customer under this nests one under an MSP. From the same menu: Edit, Users, Billing & Invoices, Add cloud credits, Suspend (their jobs stop and billing pauses; Reactivate reverses it), and Sync to Xero where accounting is connected.

Roles #

Users (per customer, from the Customers menu, or the Users page for your own tenant) adds people with a username, email and initial password and the role chips above. Every user can turn on two-factor authentication from their account menu (authenticator app, standard TOTP); the console also signs in with Microsoft or Google accounts. What every user and every AI key does is written to the Audit Trail.

Deployment tokens #

A deployment token is how a machine joins the right customer. Agents → Enroll Agent: choose the customer, an optional name for the token, and how long it lives (1 hour to 7 days; 24 hours by default). The dialog returns the token and a ready-to-paste msiexec command with it filled in.

• Tokens are single-use by default: one token enrols one machine, and a leaked token that has been used is worthless. For a batch deployment through RMM create one per machine, or ask for a multi-use token via the API (create_enrollment_token, maxUses).
• Active tokens are listed under Agents; revoke one there before it expires if it was sent to the wrong person.
• The customer is fixed by the token. A machine enrolled into the wrong customer must be uninstalled and re-enrolled; see moving a machine.

Storage targets #

A storage target is somewhere data goes (or, for a cloud-to-cloud copy, comes from). It belongs to one customer, and the customer's credentials for it are stored encrypted and never shown again. Storage → Add, choose the provider, fill in the credentials, Test. The same target can serve as a backup destination, a cloud-drive source and an archive destination.

Browse on a target lists it live; from there folders can be marked for archiving. A target whose credentials fail shows the provider's message on its row until it is fixed — that is usually the first sign a key was rotated.

Agents #

Agents lists every machine under the customers you can see, with online state (checked in within the last 90 seconds), version, platform and last-seen time. Offline is not a fault: laptops close and old machines are retired. Per machine, ⋮:

• Rename — a friendly name shown alongside the hostname.
• Properties… — how many jobs may run at once on the machine (3 by default), an upload cap in Mbps for a site with a thin line, and for Hyper-V hosts the changed-block incremental mode.
• Cloud Drives — the drives mounted on it; see Cloud drives.
• Notifications… — mute alerts for a machine that is expected to be off.
• Deactivate — for a machine that is gone. Its jobs stop, its history stays; Reactivate restores everything if it comes back.

Agents update themselves within minutes of a release; the version column shows who has and has not. A machine stuck on an old version is nearly always offline or unable to reach the console — see Troubleshooting.

Notifications #

Notifications (per customer): email addresses and an optional webhook (URL plus an HMAC signing secret so the receiver can verify it is Caryvane) for three events — job completed successfully, job failed, agent goes offline. Caryvane sends the email; nothing to set up on your side. Send test proves the route. Overrides sit on the job (Mute notifications for this job) and on the agent, for the one noisy job or the laptop that is off every weekend.

Cloud Agent jobs and credits #

Storage-to-storage copies, connector backups and archiving jobs can run on the Caryvane-hosted Cloud Agent instead of a customer's machine, so the data never passes through hardware you manage. Each is a cloud job drawn from the customer's allowance: on a paid plan it is metered; a prepay customer buys cloud credits, which you add from Customers → ⋮ → Add cloud credits. The wizard refuses to create a cloud job for a customer with no allowance, with the reason. Cloud Fleet (platform admins) shows the workers and what each is running.

Archiving Policy #

Archiving moves files that nobody has touched for a set time out of a customer's live storage into cheap storage, and records where they went. It is deliberately two separate acts, both explicit:

1. Mark the folders. Storage → the target → ⋮ → Archiving… to switch archiving on for that connection. Then Browse it; each folder gains an Archiving rule action: Archive after N days / months / years (judged by last modified, or last opened where the source reports it) or Never archive. Rules inherit down the tree — mark Finance for 3 years and every subfolder follows, except one you mark Never. Badges on the folders show the rule in force, faded where it is inherited, with the ancestor it comes from on hover.
2. Create the Archiving job. Jobs → New Job → Archiving: the marked connection, the archive destination and prefix, weekly by default. The one destructive switch — Remove archived files from the source — is off until you turn it on, so the first run is a copy you can inspect. Each run judges every file under a marked folder, copies the ones old enough, verifies the copy (hash where both sides report one, else size), records it in the catalogue, and only then — only with the switch on, only with hash or size proof — deletes the original.

Billing #

Direct customers are billed in advance; MSPs and distributors in arrears on the agents actually enrolled, at the rates set on their tenant (Customers → ⋮ → Edit; a distributor sets wholesale rates its MSPs cannot see). Billing & Invoices per customer lists invoices; with Xero connected they are pushed and reconciled automatically. A new direct customer starts on a 15-day trial without a card; connectors and cloud jobs wait for the paid plan.