CARTEMA
Open Cartema

For editors and owners

People and usage

Adding people to the workspace, their roles (several people's at once) and their role on each app, held invitations, viewing Cartema as one of your people, your own address and e-mail sender, the plan and what is used of it, and seeing how the apps are used.

Updated 2026-11-16For editors and owners of a workspace

People

Studio → People is everyone who uses the workspace, in three views:

  • Team — the workspace's own people, with their role and, if the workspace has clients, the clients each one works on.
  • Clients — the list of clients on the left, A–Z; the chosen client on the right, with its apps, its people and the workspace's team on it (see Clients below). To find one, type in Find a client or app above the list: part of the client's name, or of the name of one of its apps — any case, with or without accents, every word you type, in any order. The list keeps the clients that match; a client found by one of its apps shows that app's name under its own, so an app is found even when its client has another name. ↓ moves from the box into the list, Enter opens the first client found, Escape empties the box. The box stays above the list while the list scrolls. Add person and a person's Add to clients and Works on find clients by their apps' names the same way.
  • All — everyone once, with the level they belong to (the Team, or a client's name) and a + when they are on more than one.

Each line shows the person's name over their e-mail, their level, their role there, and their status: Active with when they were last seen, Invited (the e-mail is on its way or waiting to be used), Held (not sent yet) or Never signed in. A client's editors and viewers also show their apps as chips, each with their role on that app (see Roles per app). Administrators and owners can manage people; editors see the people they share an app with, and when the workspace keeps apps to listed people, nobody else's name reaches them.

  • Change a role by picking another one in the line: it is saved at once, and Undo in the message at the bottom puts it back. Only an owner can make someone an owner, and only an owner can change or remove another owner; an administrator sees an owner's role but cannot change it. The workspace always keeps at least one owner: to hand the workspace over, make the new person an owner first, and they can then change your role.
  • Click a person to open their panel: their role on every level, the clients they work on, the apps that lets them open, their Role per app in each client (see Roles per app), View as (see View as), the room for their private layers (a limit in MB within the workspace's plan; empty is no limit of their own; an owner's limit is set by an owner — see My layers, files and exports), whether they answer the support desk, a link to their activity, and Remove from the workspace. For a client's person, Add to clients adds them to one or more other clients you manage at once, as a Viewer in each: type part of a client's name to find it, pick as many as needed (they show as chips above the box; × or Backspace lets one go), then Add to clients. Works on finds and picks a Team person's clients the same way. Removing does not delete their account, and it cannot be done to yourself, to an owner unless you are an owner, or to the last owner. If they have private layers, choose first whether to keep or delete them. Kept, an owner removing them takes over their layers; when an administrator removes them, the layers wait for an owner under Studio → Private layers, where only owners see and take over the layers of people who left.
  • The ⋯ at the end of a line sends an invitation again, revokes it, moves a client's person to another client, or removes the person from that level. For a workspace owner it also offers Copy activation link, described under Inviting people to an app.
  • Tick several lines to change their role, move them to a client, send their invitations again or remove them together.
  • Add person: choose where — the Team, or one or more of the clients you manage — the role, a name, an e-mail and, if you like, a phone (kept on a new account; an existing account keeps a phone it has already), and how they get in — E-mail an invitation (the default: a Viewer or an Editor is one at once; an Administrator or an Owner joins as a viewer and gets the role when they accept the invitation — a new account by choosing its password, an existing account by opening the link while signed in. You never invite above your own role, only an owner invites an owner, and a client's owner is given all of its apps), or, for the Team only and in a company's workspace (never a personal one), Set a password now: the account is ready at once, and you give the person their password yourself (at least 10 characters). At their first sign-in they must choose their own password before anything else opens. Someone who already has a Cartema account is simply added with that role. A person who works for several clients is invited once: choose Clients, find each of their clients by name in the box (the clients you picked recently come first, then all of them A–Z; arrow keys and Enter work too), and they get the chosen role in every one of them; They will open lists the apps of all the clients chosen, and the e-mail names one app and the others. The Team is chosen on its own, never together with clients. An invitation to the Team names no app: the e-mail invites the person to the workspace with their role (for example You're invited to your workspace as an owner), so it can be sent before the workspace has any apps. After accepting, owners and administrators land in Studio, everyone else on the workspace's apps. An invitation into clients names one of their apps, so a client needs an app before its people are invited.
  • Search by name or e-mail and filter by level, role and status — Invitations shows everyone with an invitation still open. The filters stay in the address, so a filtered list can be shared by link.

Cartema support staff, when they work in your workspace at your request, never appear in these lists and are not counted among its people.

Clicking a person opens their panel. Under Details, the workspace's owners and administrators change the person's name, the e-mail they sign in with, and a phone number (an owner's details only by an owner). The sign-in e-mail itself is changed by a workspace owner; an administrator may change it only for an editor, a viewer or a person of a client assigned to them, who has already signed in and is not a client's owner or administrator. A changed e-mail is the person's sign-in from their next sign-in on. The old address is told who changed it, and an open invitation stays held until somebody sends it again. A name is corrected there, under Edit name, or by asking Buddy Pro ("remove the dash from the names"), by the people who manage that person — a client's owners and administrators included for their client's people — and only for an account that belongs to this workspace alone.

Inviting people to an app

On an app kept to listed people (Studio → Apps → the app → Who can open it), Invite people adds someone to that app only: their E-mail, Name, Role (Viewer or Editor) and the E-mail language (Hebrew, English or Portuguese; otherwise the workspace's). The app's administrators can invite, as well as the workspace's owners and administrators.

  • Someone new to Cartema gets an e-mail with a link to choose their password, and where to sign in afterwards. The link works once and for 7 days; after that it can be sent again. A link that was used, replaced by a newer one or taken back says so, and offers Sign in to whoever already chose their password with it. No password is ever written in an e-mail.
  • Someone who already has an account gets an e-mail saying they now have access, with a link to the app. Their role in the workspace does not change.
  • The e-mail carries your workspace's logo and name when they are set (see Branding below), with "Powered by Cartema".
  • A person invited this way sees only the apps they are listed on, and only those apps' people and data.
  • Access until (optional, empty by default; 14 days fills in the day two weeks from today) gives their access to the app an end: from the day after it they are taken off the app by themselves, and the workspace's owners are reminded three days before. The date holds from the moment they are invited, whether or not they ever accept, and is applied again when they do. Someone already on the app with no end keeps no end; it is changed afterwards on the app's page (see Who can open it). Not offered on a client's app.

An app's administrator invites only to the apps they manage, gives only the Viewer or Editor role, and sees only the invitations to their own apps.

Invitation history, linked from Studio → People, lists every invitation with its status — Held, Sent, Accepted, Expires soon, Expired, Revoked — filtered by status and app. Send again sends a new link (the old one stops working); it asks to be sure first — Send a new link? — click it again to send. Revoke cancels a link that has not been used (the person stays listed on the app until removed there). An invitation into several clients shows their names under the app; an invitation to the Team shows Team in place of an app. Removing the person from one of those clients keeps the invitation for the others.

Expired invitations. The link in an invitation e-mail works for 7 days from the moment the e-mail is sent. A held invitation never expires: its 7 days start only when it is sent. Owners and administrators see a link that stops within two days marked Expires soon, and one that passed its 7 days unused marked Expired; filter the list by either. Nobody tells the invited person that their link expired; a new link goes only when somebody chooses Send again:

  1. While some links have expired, Expired links on the Invitations page groups them by app, as Arrivals does for held invitations — for example 3 expired of 40. Click an app's name to see who would get a new link.
  2. Choose Send N again beside the app. The button asks to be sure — Send N new links for the app? — click it again. Each person gets a new link for 7 more days; their old link stays dead. Only that app's expired invitations go.

A client's owners and managers, and an app's administrator, see Expires soon and Expired too, in Studio and on the client's Invitations tab, with Send again: for them an invitation counts 7 days from when it was e-mailed, the same for everybody invited, so the list never shows who already had a Cartema account. Send again follows the same rules as sending: an app's administrator sends again only the invitations of the apps they manage, and the same hourly limit on e-mails applies. Someone who has already come in gets, from Send again, an e-mail that they have access to the app. Every send, and every send again, is recorded in Studio → Activity with the app it was for.

A daily e-mail about expired links. Each morning, when some invitation links expired since the last such e-mail or will expire within two days, the workspace's owners and administrators get one e-mail listing, per app, how many — no names — with a link to the Invitations page showing the expired ones. Nothing is sent on a morning with nothing new, and the invited people are never written to by it. It comes in each recipient's own language.

When an invitation's e-mail does not arrive, a workspace owner can choose ⋯ → Copy activation link and send the link to the person another way. It is a new link that works once, for 72 hours; any earlier link stops working, and a held invitation counts as sent from then on, with no e-mail. It is offered only for somebody who never used their account and belongs to no other workspace, and not for the workspace's owners and administrators or somebody invited to become one: they activate by e-mail. A client's owners and administrators may be given a link, including somebody invited to become one; if they are invited again with a role after the link was taken, that link stops working. Taking a link is recorded in Studio → Activity. Whoever opens the link chooses the password, so share it only with that person. If they are later placed in another workspace, that password is taken away and a link goes to them by e-mail.

Owners and administrators also choose there the Language of invitations for people whose language is not given.

Held invitations

Owners and administrators can tick Hold the e-mail when inviting: the person is added at once — listed on the app, with their role — but nothing is sent. This is how a large group is prepared before the day it should hear from you.

Until their invitation is sent, a held person gets no e-mail from Cartema at all: not the invitation, and not any other message either — notices of projects, announcements, answers from support. Once their invitation is sent, or once they have signed in, they are e-mailed like everyone else.

Sending held invitations, app by app:

  1. Open Studio → People and choose Invitation history (top right). The Invitations page opens.
  2. While some invitations are held, Arrivals at the top groups them by app. Each app shows how many people it has and how many of them are held — for example 12 held of 40.
  3. Click an app's name to open or close its list: each held person with their role on the app. The first app is open to begin with; a long list shows the first eight, and N people ↓ shows the rest.
  4. Choose Send N invitations beside the app. The button asks to be sure — Send N invitations for the app? — click it again to send. Only that app's held invitations go; the other apps stay held.

The list of every invitation, below Arrivals, sends them too: tick held invitations and choose Send selected, or Send all held (only the chosen app's, when the list is filtered by app). A workspace owner sends any of them; an administrator those of the clients assigned to them and the Team's, and Send all held says how many it left out. An invitation that places somebody in several clients is sent only by whoever works on all of them. In Studio → People, a held person's ⋯ → Send invitation now sends theirs; tick several people and choose Send invitations again to send theirs together (a held invitation goes out for the first time). If too many e-mails are sent within an hour, nothing is sent and the page says so: send fewer at a time.

Roles

Role Can
Viewer Open the apps and use the map tools; save views and drawings; print
Editor And: Studio — apps, data, styles (print layouts to see); change data from the map where an app allows editing
Administrator And: people, usage, the plan, and the workspace's print layouts
Owner The same as an administrator, and opens every app whatever its list of people; makes other owners, changes or removes them, and takes over the private layers of people who left

These are a person's roles in the workspace. On one app, a person can also have a role of their own — Viewer, Editor or Administrator of that app alone; see Roles per app.

An app can be kept to some people only, each a member or an administrator of that app; see Building apps in Studio. Within an app, a layer or a folder can be kept to chosen people, and its editing to chosen editors — see Who sees it and who edits it; the workspace's owners, administrators and editors and the app's administrators always see every layer. A person kept to some apps sees in Studio only those apps' data and their own, and anywhere in Cartema only the people of those apps: in lists, when sharing, and as the author of a drawing, a file or an edit. One workspace can so serve several customers without any of them seeing another's people or data.

Clients

A workspace that serves several customers gives each of them a client: a group of the workspace's apps and the people who use them — for example a community, a council or a company. The workspace and each of its clients use the same four roles — Owner, Administrator, Editor, Viewer — the client's one level below the workspace's.

Role in a client Can
Viewer Open the client's apps and use the map tools; save views and drawings; print
Editor And: change data from the map where an app allows editing; make their own layers in the client's apps (see My layers)
Administrator And: the client's people — invite them, change their roles up to Administrator, remove them; see and manage every layer of My layers that the client's own people made in the client's apps they have (see My layers)
Owner Everything in the client, and makes or changes its administrators and owners

Three rules hold on every level:

  1. People see their own level and what is below it — never above, never sideways. A client's people see only their client's apps, data and people. They never see another client, and the workspace's own staff do not appear in their lists.
  2. Nobody gives a role higher than their own.
  3. The level above manages the level below. The workspace's owners reach every client. Its administrators create clients and manage those they are assigned to. Its editors and viewers assigned to a client work in its apps.

Where. Workspace owners and administrators open Studio → People → Clients. A client's own owners and administrators see the same People screen one level down: their client's people are their team, with the same lines, panel and Add person (which offers every client they manage), and nothing of other clients; they open it with Manage people on the apps page. The Clients view is there even before the first client: type the new client's name under the list and press +. A client has:

  • Apps — the apps that belong to the client. Add an app moves one of the workspace's apps into it: from then on only this client's people (and the workspace people assigned to it) open it, and the confirmation says how many people listed on the app lose it. Take out returns an app to the workspace, where only owners open it until it is given to someone. Adding and taking out apps is for the workspace's owners and its administrators assigned to the client.
  • Data — the data the client's apps draw, one line per dataset: its kind, its rows, the client's apps that draw it (Manage and Open map beside each) and whether it is This client's or Shared with other places — other places draw other parts of the same table, and only the client's part is counted and shown. Someone kept to some of the client's apps sees only what those apps draw. Click a name for its fields and the layers that draw it; its table and its map open in the app. Upload puts a file into one of the client's apps — choose the app, then a folder of it — for everyone who opens that app; it is checked again when it arrives. The tab is for the client's owners and administrators, and for the workspace's owners and the administrators assigned to the client.
  • People — the client's people and their roles, as described above. Change a role, or remove someone from the client. A client keeps at least one owner, and nobody changes their own role; the workspace's owners may still change, move or remove a client's last owner, after a confirmation, as they manage every client. Under Your team on this client, workspace owners assign the workspace's administrators, editors and viewers who work on it; the client's people do not see this list.
  • Invitations — Add person with this client chosen (and any other clients you manage) e-mails someone a link to join it — as a Viewer or an Editor, or as an Administrator or an Owner, given when they accept (see above). The Invitations status filter shows who has not come in yet. Invitations work as described above, held invitations included.

Deleting a client. A workspace owner deletes a client that has no apps with Delete client, next to the client's name or at the bottom of its apps page (click, then click again to confirm). A client that still holds apps cannot be deleted: take its apps out first. Its people are taken out of it, their open invitations to it are withdrawn, and anyone who belonged to this client only leaves the workspace; the workspace's own people assigned to it stay in the workspace.

Some of a client's apps only. A client's person opens all of the client's apps unless you keep them to some. Under Apps in the client — in Add person, or in the person's panel — choose All apps of the client, or Only some apps and tick the apps (at least one); in the panel, Save apps keeps the change. They will open, in Add person, lists the apps the invitation gives. Someone kept to some apps sees only those apps, their data and their people. A new app of the client reaches only the people who have all of its apps. A client's owners always open every app of the client. Which apps someone opens is set here; what they do in each is their role in the client, or a role on that app alone (see Roles per app).

Layers for some of the client's people. In a client's app, a layer or a folder can be kept to some of its people, to all of the client, or to its editors or its viewers, and its editing to chosen editors; people who only view the app can also be named to edit one layer. The client's owners and administrators always see and edit every layer. See Who sees it and who edits it and Named editors.

Fields for the team only. A field of a dataset can be shown to the workspace team only, so that an internal code or note never reaches a client's people; see Your data.

A client's owners, administrators and editors each take an editor seat of the plan, its viewers a view-only seat.

Roles per app

A person's role can differ from app to app: Viewer in one, Editor in another, Administrator of a third. Their role in the client — or, on the workspace's own apps, in the workspace — is the default for every app; a role set on one app replaces it on that app only.

Role on an app Can, in that app
Viewer Open it and use the map tools; save views and drawings; print. Edit only the layers they are named on, if any (see Named editors)
Editor And change its data from the map, where the app's editing is on; make their own layers in it (see My layers)
Administrator And manage the app: see and edit every layer of it, add layers from the workspace's data, and look after the layers its people make in it

A client's owners and administrators manage every app of the client, so they have no role per app. Where their role would be, the app's Who can open it and their panel say so, to whoever may change it: to give them a role on single apps, make them an Editor or a Viewer of the client first — in their panel, or on the client's People page, which the app's page links to.

Seeing and changing a role:

  • Studio → People. A client's editors and viewers show their apps as chips: the app's name and their role on it — dark for Administrator, blue for Editor, plain for Viewer. A small dot on a chip means the role is set on that app rather than taken from their client role; a green pencil with a number counts the layers they edit by name. Someone with the same role on every app of the client shows one chip, All N apps: open their panel to set one app apart.
  • From the chip. Click a chip and choose Viewer, Editor or Administrator under it. The change is saved at once. As their role gives them back their client role on that app. Done (or Escape) closes it.
  • In the person's panel. Click the person: under each client, Role per app lists every app they open there, each with the same choice.
  • On the app's page. Studio → Apps → the app → Who can open it lists its People, each with their role on this app, and counts them — 12 people · 2 administrators · 3 editors · 7 viewers. In a client's app, the role of the client's editors and viewers can be changed there too. On one of the workspace's own apps kept to listed people, a workspace viewer can be made Editor or Administrator of that app alone (see Who can open it).

Who may change whose role:

  • The workspace's owners, its administrators for the clients they are assigned to, and a client's owners and administrators set the roles per app of the client's editors and viewers.
  • Nobody changes their own role, and nobody gives a role above their own.
  • An app's administrator manages that app only. They never change the client's owners or administrators, nor another administrator of the app: that is for the owners and administrators.
  • An administrator who does not change data themselves — a workspace viewer listed as an app's administrator — makes nobody an editor of it.
  • A client's people are never made editors or administrators of the workspace's own apps.

With client roles and some apps only. Only some apps (see Clients) decides which of the client's apps a person opens; the role per app decides what they do in each. When an app is taken away from a person, or out of the client, their role on it goes too. Making someone the client's owner or administrator clears their roles per app.

Seats. An app's editor or administrator, and anyone named to edit a layer, takes an editor seat of the plan. When the plan has none left, the change is refused: The plan has no editor seat left.

Access to layers

A person's panel shows, under Access to layers, what they see and edit in each of their apps — layer by layer — so you do not have to open every layer's rights to find one person.

  1. Open Studio → People (a client's owners and administrators: Manage people on the apps page) and click the person.
  2. Under Access to layers, each app they open shows a line: All layers (manages this app) for someone who manages its layers, otherwise how many layers they can Edit, View, and how many are Hidden from them.
  3. Click an app to unfold its layers. Each layer says what the person has and where it comes from: Everyone in the app, Their role, Their client, Named on it, from folder …, Named editor — and, where they only see a layer, why they do not edit it (Only views the app, Not on who edits it, The layer's Editable is off).
  • Filters. Choose an app, a level (Edit, View, Hidden), Named on the layer only, or type part of a layer's name. Folders open to show what matches.
  • Changing it. Choose ⋯ on a layer or folder: Can view, Can edit or Take off this layer, then Confirm. The person is added to that layer's own list (if it took its list from a folder, the list is copied onto the layer, so nobody else's access changes), or named as an editor of it — which takes an editor seat if they hold none. Each change saves a new version of the app and is written in Studio → Activity.
  • What is not theirs alone. Access that comes from everyone in the app, from their role or from their client cannot be taken from one person here: the panel says where it comes from, and Open the layer's rights takes you to the layer, where it is set for everyone.
  • Who can. Whoever manages the app's layer rights, for the people they manage: the workspace's owners for anyone; its administrators for its editors and viewers and the people of the clients they are assigned to; a client's owners and administrators for that client's people, in that client's apps. A workspace that keeps everyone but its owners to data leaves this to its owners. Nothing can be changed during View as or while the workspace is read-only, and nobody changes their own access.

View as

View as shows Cartema exactly as one of your people sees it — their apps, their layers, what they may open and do — so you can check their access without asking them.

  1. Open Studio → People (a client's owners and administrators: Manage people on the apps page) and click the person.
  2. At the bottom of their panel, choose View as. Their apps page opens, as they see it.
  3. A bar at the top of every page says Viewing as name (role) — read only · until time. Choose Exit in the bar to go back to your own account.
  • Who can. The workspace's owners, for anyone in the workspace. Its administrators, for its editors and viewers and the people of the clients they are assigned to — never an owner or another administrator. A client's owners, for that client's people; its administrators, for its editors and viewers. Nobody views as themselves or as someone who can do more than they can. View as is shown only where it is allowed.
  • Read only. Nothing can be saved, changed, downloaded or started during a view: no edits, imports, exports, prints or jobs. Buddy himself is not shown; for an owner or administrator his window opens with Buddy Pro alone, answering as the person.
  • 30 minutes. A view ends by itself after 30 minutes. The bar then says so; Exit brings you back. Signing out is not offered during a view: choose Exit first.
  • Recorded. Starting and ending a view are written in Studio → Activity under your name, with the person's: Began viewing as someone and Stopped viewing as someone.
  • Nothing changes for the person. They are not told and get no e-mail; their sign-ins, what they have read and what is new for them stay as they were. Their messages, support conversations included, are not shown.

During a view you see everything the person sees, their own layers and drawings included, read only.

Branding

Branding is available on request: Cartema support turns it on for a workspace.

Studio → Branding, for the workspace's owners and administrators: two logos, each optional (PNG, JPEG, WebP or SVG, up to 5 MB), and the name shown with them.

  • Product logo — in the header of every page and above the form on the sign-in page your people reach through your sign-in link, shown on the same page, each with a small "Powered by Cartema" line. A logo on a transparent background reads on both light and dark pages.
  • Company logo — shown large on the sign-in page's map picture, in place of Cartema's mark, with your name below it. The picture is dark in both themes, so a white or light version of the logo reads best. Without a company logo, the product logo is shown there.

Remove takes a logo away; with neither set, Cartema looks as it did.

Your own address

A workspace can also open at an address on your organisation's own domain, such as maps.example.com. Ask Cartema support for it: they tell you the DNS record to add (a CNAME pointing at Cartema; with Cloudflare, set it to DNS only), and once it is in place the address works with its own secure certificate. Your sign-in link is then that address. There, your people see only your workspace, with your logos on the sign-in page and your product logo as the browser tab's icon; signing in there is separate from signing in at cartema.mdvia.am, and invitations to your workspace bring people to your address.

E-mail from your own address. The e-mails Cartema sends on your workspace's behalf — invitations, Projects messages, tasks and digests, your own support desk's conversations, notices to the owners — can come from an address of your organisation, such as noreply@maps.example.com, rather than from Cartema's. It helps where your people's mail servers accept only known senders. Ask Cartema support: your domain needs the DNS records they give you, so that receiving servers accept the mail as yours. Conversations with Cartema support and Cartema's own messages to everybody still come from Cartema.

Your own support desk

An organisation that supports its own people — or its own customers in one workspace — does it in Cartema. The first place is Projects (see Projects): each app's tasks and its conversation with the people who look after it; whoever sees Projects without working in Studio reaches it with Contact us. How-to questions go to Buddy, the in-app guide. Every message reaches a person: there is no automatic answer in a conversation.

For the people who do not see Projects, Projects → Settings (administrators and owners) also has:

  • Our workspace answers its people's questions — on, and conversations started with Contact us in the workspace go to your support desk instead of Cartema support. Cartema support can still read every conversation, and you can bring it in on any of them with Ask Cartema support too. Your own desk's people write to Cartema support as before.
  • Who answers: the workspace's owners and administrators. To choose others, open a person in Studio → People and turn on Answers the support desk; the owners always answer too. They see the conversations written to the desk under Messages → Support desk, with the person's name, and the bell and an e-mail tell them of new messages. Nobody else sees them, and a person never sees another person's conversations.
  • Buddy, the in-app guide — where Buddy is available to your workspace. Turn it off and Buddy is not shown to anyone in the workspace. Each person accepts Buddy's notice before their first question; what it says is in the privacy policy.

Nothing written in a conversation can be changed or deleted, by anybody. Support closes a conversation that is done; the person writing in it again opens it.

Plan and usage

Studio → Plan and usage (administrators and owners) shows what the workspace's plan includes and how much of it is used, each with a bar: editors and view-only users (or accounts, below), apps, storage, and the photos processed into orthophotos this month. Monthly counts start again on the date shown.

  • At 75, 90 and 100 % of a limit, the owners and administrators are e-mailed, and a banner across Studio says so.
  • A limit that is reached holds: no one is added beyond the seats (nor given a role that would need one), no new app is made, uploads stop when the storage is full, and drone processing stops for the month. Storage and processing can go on with pay as you go; more seats and apps are asked for.
  • Extra usage: with Allow usage beyond the plan (pay as you go) — an owner's choice — storage and drone processing can go past the plan and are charged for what is used. A Monthly limit caps the extra charges; empty is no limit. This month so far shows what has been used beyond the plan; it is charged on the next invoice.
  • A licence of accounts: some plans include a number of Accounts in all — editors and view-only users together, the people of every client of the workspace included — instead of separate seats. The bar then shows Accounts (editors and view-only users). When the plan prices blocks of accounts beyond the licence, people can still be added past it: every started block (100 accounts, say) is charged a month at the plan's block price, counted at the month's highest number of accounts, and the line under the bar shows this month's extra blocks and that peak; they appear under This month so far and on the next invoice. Without a block price, no one is added beyond the licence. Cartema support's own accounts never count.
  • Get more: ask Cartema for more accounts, editors, view-only users, apps or storage, or a bigger plan — What, How many, a Note, Send request. The answer comes by e-mail; what is granted goes onto the plan and the next invoice. Requests for more lists them with their status.

Storage by kind

Under the bars, Storage by kind shows what the storage is made of, from the last hourly measurement: Orthophotos and rasters (raster collections included), Elevation models (DTM, DSM), 3D models, CAD drawings, Vector layers (database), Attachments and photos, Drone flights (photos and products), Original files kept, Printed maps (PDF), Field packs and Other and system — each with its size and its share of the plan's storage (of the storage used, when the plan sets no limit), biggest first, over one bar. The kinds add up to the storage figure above them.

The storage is one figure for the whole workspace: its layers, images, 3D models and files, and the original files kept for it (the sources its data was loaded from, for example), all counted together in their kinds. Nothing is counted twice and nothing is left out.

Largest items lists the ten biggest things you may see — datasets, 3D models, drone flights' photos and, for the workspace's owners and administrators, the original files kept for it, each by its name with the kind it counts in. Click a dataset to open it in Studio → Datasets with its properties; a 3D model opens its app, a flight its orthophoto page.

A workspace without plan limits says so, and nothing is counted against it.

Buddy usage

Buddy's use is shown as a share of what the plan includes this month, the way AI assistants show a plan's usage: for example Buddy Pro · 64% used, and the date it resets. Answers Buddy knows by heart — where a button is, a guided tour, Cartema's ready answers to common questions — use none of it. Buddy is the only AI in Cartema: conversations with support and on Projects are answered by people.

Why a share and not a count:

  • different AI models cost very differently, so the same count would mean different things;
  • most of the work behind an answer is not seen: the help and the data Buddy reads before he answers;
  • what one request takes changes as Cartema improves (it remembers what it read, and learns where to look);
  • a share of the plan is what people understand.

The exact numbers are kept: Cartema support sees them, and an invoice for extra usage lists them exactly.

Studio → Plan and usage has a Buddy row laid out like an AI assistant's usage page. Under Your usage and the plan's name:

  • Buddy — the month's whole allowance: Resets and the date, a bar, and how much of it is used (for example 6% used). The bar turns amber from 75 % and red from 90 %.
  • Buddy Pro, set in under it — its own use, or Buddy Pro is not included in this plan. A plan that includes no Buddy says so in the same way.
  • Heads up — when this month's pace so far would use the allowance up before it resets, a line says on which day (for Buddy, or for Buddy Pro's part).
  • Your use — when the plan limits one person's use over a few hours, your own share of that limit and when it resets.

Some plans share one monthly allowance between Buddy and Buddy Pro, with Buddy Pro limited to part of it. On such a plan, the Buddy bar counts what both have used, the Buddy Pro bar counts Buddy Pro's use of its part, and the line under its name says how much of the allowance Buddy Pro may use (Up to 50% of your monthly allowance) and when it resets. Once its part, or the whole allowance, is used, Buddy Pro's bar shows 100% used.

Under the bars, Extra usage: for Buddy and for Buddy Pro, whether extra usage is on or off, with the monthly limit for extra usage when one is set. The workspace's owners (and Cartema support) also have See more: by client and by person, which opens the details on Studio → Usage. What extra usage comes to so far is counted under Extra usage, in what the month comes to beyond the plan.

  • Once the month's share is used, Buddy still shows where things are and walks people through tasks, but stops looking things up and says that the workspace's allowance for the month is used, until the date shown.
  • At the allowance is the owners' choice, for Buddy and for Buddy Pro separately: under Extra usage, choose Continue as extras, billed with the monthly invoice or Stop until next month, type a Monthly limit for extra usage if you want one, and Save. Stopped, Buddy Pro says that the month's allowance is used, and Buddy keeps guiding. With extras, Buddy then carries on past the month's allowance, and the extra usage is charged on the invoice for that month; the invoice line shows exactly what was used and what it came to. Nothing past the monthly limit is charged: at the limit, Buddy stops looking things up until the month renews. Empty is no limit. Administrators see whether extra usage is on, not the switches.
  • At 75, 90 and 100 % of the month's allowance, and of the monthly limit for extras, the owners are e-mailed and a banner across Studio says so.
  • A plan may also limit how much one person uses within a few hours, so that nobody uses up the month for everybody; the line under the row's title then says so, as a share of the month's Buddy, and Your use shows your own share of it and when it resets. Buddy answers from what he knows by heart until the hours have passed.
  • Cartema support's own questions to Buddy in your workspace are never counted.

Usage

Studio → Usage (administrators and owners) shows the last 30 days: for each person, when they were last seen, how often they opened a map and for how long, how many layers they switched on, what they identified and printed, the layers they used most, and by app. Visitors of public apps are counted together as one row. Click a person for their history.

Under them, Buddy and Buddy Pro is for the workspace's owners only (and Cartema support): the month's use as bars, the same as the Buddy row on Plan and usage, and under them See more, closed until you open it, with the details — each client's share of the month (as on the client's Usage tab), then each person's use as their share of what the plan includes (Buddy Pro's tasks included, under Buddy Pro), so the people's shares add up to the share on Plan and usage — where the plan includes none, as their share of the use shown — and the tasks Buddy Pro did for them after they confirmed them (Jobs run). Choose All, Buddy or Buddy Pro in the list above the people. A client's Usage tab shows the owners that client's share as bars, with its people under See more. Administrators, editors and viewers, and a client's own owners and administrators, see no one's AI use: the tab and the section are not there for them. The allowance renews on the first of each month, and nothing carries over. On Studio → Usage, Time saved is a cautious estimate of how long the tasks Buddy Pro did this month would have taken by hand: the whole team's over the bars (administrators see this line too), and each person's under See more.

Usage records hold what was opened and switched on, not where anyone clicked; see the privacy policy.

Activity

Studio → Activity (administrators and owners) is what the workspace's people did, and in which role: sign-ins, apps opened, prints, features added, edited and deleted, imports and deliveries, changes to apps (who opens them, their editing and their visibility included), styles, layouts, plan sheets and members, private layers submitted and accepted, files of meters, field packs (with their app and how many layers each carries), drone flights. Look back 7, 30 or 90 days, and narrow it to a role, a person or a kind of action; the counts and the chart by role sit above the timeline. Work done by Cartema support shows as MDVIA; people who have left, as Former member. An administrator who works on some of the workspace's clients, or is kept to some apps, sees only the lines of those apps, clients and people.

Jobs

Studio → Jobs shows imports, deliveries, print runs and orthophoto processing — Queued, Running, Done or Failed — with a log that explains any error or warning. A job that made a dataset names it, and the name opens the dataset. Search, and filter by job and status, when the list grows.