People and usage

#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; the chosen client on the right, with its apps, its people and the workspace's team on it (see Clients below).
• 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. 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, 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.
• 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 and an e-mail, 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, Set a password now: the account is ready at once, and you give the person their password yourself (at least 10 characters). 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.
• 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.

#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 managers 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. The link works once and for 7 days; after that it can be sent again. 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.

An app's manager 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, Expired, Revoked — filtered by status and app. Send again sends a new link (the old one stops working); 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. Removing the person from one of those clients keeps the invitation for the others.

Held invitations. Owners and administrators can tick Hold the e-mail when inviting: the person is added at once, but nobody is e-mailed until it is sent from Studio → People (the person's ⋯, or several ticked together) or with Send all held in the invitation history. This is how a large group is prepared before the day it should hear from you. Owners and administrators also choose there the Language of invitations for people whose language is not given.

#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

An app can be kept to some people only, each a member or a manager of that app; see Building apps in Studio. 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
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.
• People — the client's people and their roles, as described above. Change a role, or remove someone from the client. A client always keeps at least one owner, and nobody changes their own role. 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.

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.

#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; signing in there is separate from signing in at cartema.mdvia.am, and invitations to your workspace bring people to your address.

#Your own support desk

An organisation that supports its own people — or its own customers in one workspace — can answer their questions in Cartema. In Studio → Support (administrators and owners):

• Our workspace answers its people's questions — on, and every new conversation started with Contact us in the workspace goes 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 tells them of new messages. Nobody else sees them, and a person never sees another person's conversations.
• An automatic assistant answers first — the support assistant (see Questions and answers). Turn it off and every question goes straight to a person.
• 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.
• Scripted answers: the questions your people ask often, each with your answer and other ways of asking it, one a line. The assistant gives one of these, at no cost, when a question is close enough to it. Cartema's own answers to common questions about Cartema are always offered after yours.
• This month shows how much the assistant was used. It has a monthly allowance; when that is used up, only scripted answers are given, and then a person.

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, view-only users, 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.
• Get more: ask Cartema for more 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.

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

#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.

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, styles, layouts, plan sheets and members, private layers submitted and accepted, 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.

#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.