Unlock
This console is locked with a passphrase. Without it the stored sign-in cannot be used, so somebody sitting at this computer cannot simply open the page.
Forgotten it? There is no reset — it never leaves this browser. Start again with an enrollment code.
Sign in
Or paste an enrollment code. The console signs in the same way a phone does — there is no separate admin login to keep in sync.
No code, and nobody to make you one? If your email is on the roster, we can send you one.
History
Who did what, to whom, and when. Every entry is sealed to the one before it, so a changed or removed row can be detected — that is what “check the record” below does.
Press Show.
On the TAK server
Everyone on the TAK server who belongs to your agency but is not on this roster yet. Adding them here does not create or change anything there — their account and channels stay exactly as they are. It puts them on your roster so you can page them.
Connected now
Live from the TAK server. This is not the roster — somebody can be connected without being on it, and that is worth knowing.
Loading…
Files on the TAK server
Things people can pull down from the server — icon sets, map overlays, map sources. Not the setup package somebody gets when they enroll; that one is under Files.
This is everything on the server, not just your agency’s. The TAK server keeps one store shared by every agency on it, and marks each item with the channels that can see it.
Put a file on the server
Everyone on this server will be able to see it. The TAK server decides that from the account this console signs in with, and there is no way to limit it to one channel or one agency. After it uploads, we show you exactly which channels it landed in.
It has to be a .zip data package, up to 50 MB.
Loading…
Data Sync
A shared folder that also carries live map markers. People subscribe to one and see it change as it changes.
Make a shared folder
Pick the channel carefully. Only people in that channel can see the folder — and if you leave it blank the TAK server shares it with everybody on the server, so we ask you to choose.
No spaces — use dashes or underscores. The name becomes the folder’s address on the server, so it cannot be changed later. Put the full wording in the description.
Loading…
Certificates
Which devices hold a badge for your TAK server. A badge belongs to a device, not a person — one login can hold several, one per handset.
Loading…
Channels
Who can hear whom. Laid out like the channel list you already know.
Loading…
Templates
A named set of channels — "Patrol" hands somebody four of them in one click when you enroll them.
A template is copied, not attached. Choosing one puts its
channels on that person there and then, and nothing remembers it
afterwards. So changing a template later changes what the next
person gets and touches nobody already enrolled — and deleting one takes
nobody's access away.
Sentinel keeps a template attached and re-syncs everyone on it;
we deliberately do not — an edit there is an invisible mass change to
people who are not on screen.
Loading…
TAK activity
What the TAK server itself wrote down — sign-ins, connections, and changes made on the server, in its own words. Different from History under Administration, which is what this console recorded. When the two disagree, this one is the server's side of the story.
Loading…
Error log
This console's own error report. When a screen breaks, a text does not send, or an enrollment fails, the reason lands here. It is the screen to open — or send to us — to find out why something went wrong.
Empty is good. It fills up when something goes wrong, so a blank page means nothing has since the last restart. Not the same as TAK activity, which is what the TAK server wrote down, or History, which is the record of what people did. One caveat: it only covers since the last restart, so if the service failed to start at all, nothing here will show it.
Loading…
Agencies
Each one is a separate roster. People, channels and history do not cross between them.
Loading…
Server Health
What is working, and more importantly what is quietly not. A broken database announces itself; push notifications being switched off does not — every screen looks perfect and nobody gets paged.
Checking…
Agencies that want a look
Only agencies with something outstanding are listed. An agency with no default channels cannot enroll anybody at all — the TAK server refuses an account that is in no channel.
Users
One list of everybody — people on any agency’s roster AND accounts on the TAK server, together. Search by name, call sign, login, email or phone; you do not need to know which agency they are on, or which of the two they came from.
Missing is how you work a gap as a list. “No email address” is exactly who cannot use work-account sign-in; “no mobile number” is exactly who a page will never reach.
Removing somebody wipes their name, so a removed person shows up as Removed member with nothing on the row. Searching for who they were will not find them — pick their agency instead.
Loading…
Live nets
Every net on the radio right now, the way a phone sees them. Operation nets come and go with an event; standing nets are always there. Built to be glanced at — the tree is edited on Standing Nets.
Comm plans
The radio plan your agency agrees on in daylight — what an ICS-205 would carry. Write it once here; during a callout one button builds the whole net structure, named and ordered. Nobody designs a radio plan at 3am.
Nothing here is live. A plan is a pattern, not running radio. Press Start a callout on one and it opens Live Nets with that plan chosen — you name the callout, pick who is on it, and the nets land on their phones. Ending the operation there packs them away again.
Standing nets
The everyday radio tree that is always there — the opposite of an operation, which comes and goes. This is where the tree is built and ordered; Live Nets is where you watch it.
Who is actually on each net is on Live Nets, drawn on the nets themselves rather than listed twice.
Guide
How to run this, in the order you will actually need it. Nothing on these pages changes anything.
Nothing matches that.
What this is
This is the desk side of your TAK system. You bring people in here, decide what their phone gets set up with, and call them out when something happens. The phone side is the app.
You add somebody once. They get a code, and that one code sets up their whole phone — their TAK login, their channels, their map settings, their place on the roster. After that you can page them, give them radio nets, and send them files, all from here.
The five things you will use
- Enroll — bring somebody in and hand them a code.
- Device setup — decide what a phone gets set up with.
- Dashboard — the roster, and everything you do to one person.
- Send an activation — call people out and see who answers.
- Live Nets — radio channels for an incident.
Signing in
You sign in with a code, the same way a responder's phone does. There is no separate admin password to keep in step.
A code works once, on one device. That is deliberate: a code that works twice is a code that can be forwarded.
Setting this computer up
- Paste the code and press Sign in.
- Go to Settings and set a passphrase.
The passphrase is what makes this computer safe to leave. Without it, anybody who sits down at your desk is signed in as you. With it, the stored sign-in is locked and useless until somebody types it.
If you are locked out
- Somebody else is signed in? Ask them to find you on the roster and press New code.
- Nobody is? Use Email me a code on the sign-in page. If your email is on the roster, a code arrives. It works once and expires in 30 minutes.
First twenty minutes
Start to finish, for a brand new agency.
Five steps, on the real screens. Stop any time.
- Set the agency default. Device setup → Packages → Agency default → Edit. This is what everybody gets unless a package says otherwise. Set the default channels first — they decide who each person can see and hear — then the map key, coordinates, toolbar and team names.
- Upload your files. Device setup → Files. Icon sets, terrain, map sources. Once here, available to every package.
- Make a package. Device setup → New package. A package is what a kind of person gets — SWAT, Patrol, Volunteer.
- Bring one person in. Single Enroll. Pick the package. Hand them the code.
- Check it landed. Device setup → Who has picked it up.
Who can do what
Six levels. The first three are the ones you will actually hand out; the last two exist because somebody has to run the server.
TAK User
Everybody else. They see their own details, pull their own setup file and QR code, and see the roster — names and callsigns, which is what a phone shows anyway. They do not see other people’s phone numbers or emails. A responder’s phone has no reason to carry the whole agency’s contact list.
Dispatcher
Works this console and carries no phone. Starts and cancels callouts, runs the radio nets, sees the roster with contact details, and reads the agency’s history. Touches nothing on the roster: no enrolling, no editing, no channel changes.
Enrollment Admin
Whoever is running the sign-up desk at a training day. They bring people in and reset passwords, all day. They cannot edit somebody, remove their access, or revoke a certificate.
Agency Admin
Runs one agency. Everything above, plus editing people, removing access, revoking certificates, setting phone settings, making packages, and making channels for their own agency. This is what almost everybody should be, including the person who runs the busiest agency on the server.
Site Admin
The organization paying for the server. Everything an Agency Admin can do, in every agency on this deployment, plus:
- Making and archiving agencies.
- Moving somebody from one agency to another.
- Making channels for every agency (Global), and marking a channel sensitive.
- Putting a file on the TAK server, or a Data Sync folder.
- Setting up video streams and the voice server.
- Server Health and the Error log.
- Seeing the whole server — every account on it.
- Making other Site Admins, and Agency Admins anywhere.
Global Admin
Us. Everything a Site Admin can do, plus exactly two things, and they are grouped for one reason: they destroy something permanently and no screen anywhere puts it back.
- Deleting an agency outright. Archiving does everything else — blocks sign-ups, removes access, hides it from the lists — and keeps the record. Deleting erases the history.
- Deleting an account off the TAK server. This is the one that can remove the account this console signs in with, or the server’s own administrator.
A Global Admin cannot be granted from inside the console — not even by another Global Admin. It is set on the server itself, and not because we distrust anybody: if a Global Admin’s session is ever stolen, the attacker already has everything. What they do not have is a way to leave a door open behind them. Keeping this off every screen means you can revoke the stolen account and be finished.
Sensitive channels
A channel can be marked SENSITIVE. Everybody still sees that it exists and that it is marked — only Site Admin and above can see who is in it or change it.
Controls you cannot use are not drawn at all, or are drawn switched off with the reason on them, rather than shown and then refused. If a button you expect is missing, that is usually why.
Agencies
An agency here is a separate roster with its own settings, packages and people. One TAK server can carry many of them — that is the usual shape for a county or a mutual-aid group.
Making a new agency creates a whole new roster, so it takes an operator who covers the deployment rather than one agency. Everything else on that agency’s settings can be changed afterwards.
Bringing people in
Four ways in. Pick by how many people are in front of you.
Single Enroll
One person you are looking at. Name, mobile, package. They get a link and a code.
Group Enroll
A room full of people at once. One code everybody uses; you decide in advance what role, channels and package they all get. Good for a training night.
Bulk Enroll
A list from a spreadsheet. It shows you exactly what it is going to do before it does it, so paste first and read the preview. Everything you set — package, role, team, app — applies to every row.
On the TAK server
People who already exist on the TAK server but are not on your roster here. Adopting one links the two together rather than making a duplicate. Use this when somebody already has a TAK login.
ATAK, WinTAK and other apps
Not everybody runs R2TAK. You can enroll somebody on any TAK app, but how their settings reach them is different, and that catches people out.
Two ways settings travel
-
The data package — a file they import.
Certificates, icon sets, terrain, map sources, and a
.prefsettings file. - The phone settings — sent when the app signs in to this system. Toolbar, units, team names, geofences, quick chat.
Only R2TAK uses the second one. ATAK never talks to this system at all — it talks to the TAK server. It only ever sees the package.
Who gets what
| App | Certificates | Icons & terrain | Map sources | .pref | Phone settings |
|---|---|---|---|---|---|
| ATAK | Yes | Yes | Yes | Yes | No |
| WinTAK | Yes | Yes | Yes | Yes | No |
| R2TAK | Yes | Yes | Yes | No | Yes |
| TAK Aware | Yes | Yes | Yes | No | No |
| iTAK | Yes | Yes | No | No | No |
| CloudTAK | Yes | Yes | No | No | No |
Enrolling somebody on ATAK or WinTAK
- Make the .pref once. Set an ATAK device up the way you want it, then export its preferences from ATAK. That file is your template.
- Upload it. Device setup → Files → "Settings file (.pref)".
- Make a package for them. Set TAK app: ATAK, and check the .pref along with any icon sets and map sources.
- Enroll them on that package — Single, Group or Bulk, all the same.
- They get an email with ATAK's own setup steps and a package holding their certificates and files. They import it, and ATAK applies the settings.
TAK Aware, iTAK and CloudTAK
These have no settings channel at all. They do not read a .pref, and they do not sign in to this system. All we can give them is certificates and files — their users set the app up themselves.
That is not something to fix here; it is what those apps support. Worth knowing before promising anybody a consistent setup.
One caution about .pref files
A .pref can point a device at a different server. That is why R2TAK ignores them — a package can arrive from anywhere, and it is not checked the way the phone settings are.
For ATAK that risk is simply how ATAK has always worked. Just do not treat the two as equivalent: one is a file anybody could hand somebody, the other only ever comes from here.
The roster
Everybody, and everything you can do to one person. On the Dashboard.
- New code — they lost their phone, or never enrolled.
- Package — move them onto a different setup.
- Permissions — what they can do in here.
- TAK password — reset it; they set their own after.
- Disable — stop their access without deleting them.
- Remove — take them off the roster.
Teams
A team is a name you can page all at once. That is the whole job.
Teams live at the bottom of Send an activation, because paging is the only thing they are for. Make a team, add people to it from the dropdown, and it becomes something you can pick when you send.
Click a name to take somebody off. Worth doing when people move on — otherwise they keep getting called to incidents that are no longer theirs.
Packages
A package is what a kind of person gets set up with — SWAT, Patrol, Volunteer. You pick one when you enroll somebody instead of setting the same nine things again.
Agency default is the fallback for anyone with no package, and the base the others build on.
What adds, and what replaces
- Channels and files ADD to the agency default.
- Everything else REPLACES it — toolbar, hidden tools, units, coordinates.
The three states, on every setting
- Switch off — we say nothing, the phone keeps what it has.
- Switch on, nothing chosen — a deliberate empty. An empty toolbar is a real instruction.
- Switch on, things chosen — exactly those.
Moving somebody between packages
Change the Package column on the roster. Their phone picks it up on its next check-in — no need to re-enroll them.
Files
The library the packages draw from. Upload once and it is available to every package.
- Icon set — a zip of map icons.
- Map source — an XML file describing a map layer.
- Terrain (DTED) — elevation data.
- Settings file (.pref) — Android and Windows only.
Everyone means it goes out with every enrollment whether a package names it or not. Unchecked, it goes only to the packages that ask for it.
Phone settings
Set on the agency default, or on a package to differ from it.
- Units — distance, altitude, speed, temperature. Display only.
- Toolbar — which tools are on the bar, in order. Around seven fit.
- Tools grid — the full page of tools behind the toolbar, in order.
- Hidden tools — off the bar and out of the menu, still in the phone's own settings.
- Quick chat — canned messages. The button text and what it sends are different on purpose.
- Geofences — alerting behavior, and how far out to warn.
- Toolbar colors — with a preview, because white icons on a light map look like missing tools.
Team names
What your people see instead of a color — Cyan is "Alpha", Green is "Medical". The color itself is fixed and shared with every other TAK app; only the word is yours. Agency-wide.
Who has picked it up
After you change a setting, this is how you know it landed. Three states:
- Current — they have what you would give them now.
- Stale — they have an older setup and will update on their next check-in.
- Unknown — we have never heard from that phone.
Calling people out
Send an activation. Say what is happening, pick who, send. Then watch the answers come in.
Who
Search finds both teams and people. Pick a team to page everybody on it; pick people to page just them. You can mix.
How it reaches them
- App notification — right away.
- Text — after two minutes, if they have not answered.
- Phone call — after five minutes, if they still have not.
Somebody who answers stops climbing that ladder. Somebody with no mobile number only ever gets the first rung.
Who has answered
Live, under the send form. Responding, not responding, and who has said nothing at all — the third one being the group worth chasing.
Radio nets
Three screens, and they do different jobs.
- Standing Nets — the channels your agency has every day. Set up once, left alone.
- Comm Plans — a saved pattern of nets for a kind of incident. Stamp it out when that kind of thing happens.
- Live Nets — what is running right now, from a plan or built by hand. Packed away when the incident ends.
Starting an operation from a plan makes the nets and puts them on the right phones. Ending it removes exactly what it made and nothing an operator built by hand.
Channels
A channel is a group on the radio. Being in one is what decides whose map markers and messages somebody sees, and who sees theirs. Everything else on a phone is settings; this is the part that decides who they are working with.
The three ways to be in one
The same three words, arrows and colors Sentinel uses, so somebody who administers both does not have to translate.
- Both ↔ — they see the channel and the channel sees them. This is what most people want.
- Write ← — the channel sees them, they do not see it. Useful for somebody whose position you want on the map without filling their screen.
- Read → — they see the channel and it does not see them. Useful for a watch desk.
The description on each channel is ours, not the server’s — the server has nowhere to keep one. It is there so the next person to look knows what CCSO-TAC1 is actually for.
Changing somebody’s channels replaces the whole list rather than adding to it, so the screen always shows you every channel they will end up with. Taking away their last channel is refused: that leaves somebody connected but deaf and mute, which looks like a working account and is not. Use Remove if you mean to take their access away.
Files on the TAK server
Icon sets, map overlays, saved markers — anything you want people to be able to fetch on their own. It is a zip file, up to 50 MB.
Everyone on the server can see it
Everyone on this server will be able to see it. The TAK server decides who can see a file from the account this console signs in with, and there is no setting to narrow it to one channel or one agency. So a file you put here is visible to every channel on the server, including other agencies’ channels. That is why only a Global Admin can add or remove one, and why the screen tells you which channels it landed in as soon as it is done.
Removing files
Check the boxes and press Remove selected. One thing to know before you do:
There is no undo. A phone that already downloaded a file keeps its copy; it just cannot fetch it again.
Rows you did not put there
Some rows say left over from a shared folder. The TAK server takes a snapshot whenever a Data Sync folder is made, and it leaves that snapshot behind after the folder is removed. They are real files taking real space and they are safe to remove. They are labeled rather than hidden so nobody spends an afternoon wondering where a file they never uploaded came from.
Data Sync
A shared folder that also carries live map markers. People subscribe to one, and everything in it — files, markers, notes — changes on their screen as it changes. The closest everyday comparison is a shared drive that also holds the map.
Good for one callout, one exercise, or one standing job that several agencies work together.
Pick the channel carefully
The name cannot change later
The name becomes the folder’s address on the server, so it is fixed once it is made and it cannot contain spaces. Use dashes or underscores — Cobb-County-Callout — and put the plain wording in the description, where it can say anything you like.
Removing one
Everything in the folder goes with it, and everybody subscribed to it loses it. There is no undo. A snapshot stays behind in Server files, which you can remove separately.
Who is on the server
Three screens that answer three different questions. They look similar and they are not.
Certificates
Which devices hold a badge for your TAK server. A badge belongs to a device, not a person — one login can hold several, one per handset. Somebody with two badges usually has an old phone still on the list.
Connected now
Who is on the server this minute. This is deliberately not joined to your roster: a device can connect with no account of yours behind it, and those are exactly the rows worth looking at.
Whole server
Everyone the TAK server knows about, across every agency on it — not just your roster. Use it to find people who had a TAK login before this system existed, and adopt them onto your roster rather than making a duplicate.
When something looks wrong
A change has not reached a phone
Check Who has picked it up. A phone updates when the app checks in, not the moment you press Save.
A code will not work
- Capitals and the hyphen do not matter.
abcd efghis fine. - A code works once. Press New code for another.
- If that phone is already signed in, sign out on it first.
The channel list is empty or out of date
That list comes from the TAK server. If it did not answer, the screen says so rather than pretending — the last good answer is shown and marked.
Somebody did not get paged
Look at Sent. Every attempt is recorded with what happened. No mobile number means app notification only.
Who did what
History. Every change, who made it, and to whom. It can be checked for tampering from that screen.
A screen says it could not read the TAK server
That is a different thing from the server being empty, and no screen here draws an empty table to mean it. Channels, Server files, Data Sync and Certificates all say so plainly instead. The usual cause is the TAK server being restarted or unreachable for a moment; opening the screen again is the first thing to try.
The channel list will not fill in
The console reads the channel list once when you sign in. If the server did not answer at that moment, some pickers stay empty for the rest of the session. Reload the page and it asks again.
A file is still listed after removing it
The screen says so rather than telling you it worked, because the TAK server reports a removal as done whether or not it did anything. Try once more. If it stays, the server needs looking at — nothing here can force it.
A button is missing that you expected
Adding or removing anything on the TAK server itself — files, shared folders, agencies — takes an operator who covers the whole deployment, not one agency. Those controls are not drawn at all for anybody else rather than shown and then refused. If you should have them and do not, somebody has to grant it from the server.
Not built yet
Said plainly, so nobody hunts for a button that is not there.
- Aircraft and vessel feeds — the tools exist on the phone and there is nowhere to put the account details yet.
- Per-package team names — team names are agency-wide for now.
- Pinning a map point from here — the activation screen has no map picker yet.
- Taking push to talk back — it goes to everyone, and hiding the tool is how you take it off a toolbar.
- Putting files into a Data Sync folder from here — you can make the folder and choose who sees it; filling it is done from the phone.
- Files bigger than 50 MB on the TAK server — map tile packs run to hundreds of megabytes and need a different way of sending them.
- Changing the video password from a screen — the video server forgets it on restart, so it is an operator command on the box instead of a button that would quietly undo itself.
About this agency
Used on screens and printouts where the full name will not fit. None of it is required.
TAK logins for this agency
A login is worked out from a person's name — John Doe becomes
jdoe. If another agency on the same TAK server already has
a John Doe, the server refuses the second one. Adding a short tag to the
end keeps them apart.
Branding
Your logo and a notice line, shown across the top of this console.
Your other tools
Links to whatever else this agency runs — dispatch, mapping, the TAK server's own page. They show up in the menu so the next person on shift has them too, instead of living in somebody's browser bookmarks.
Default channels
What everyone joins unless somebody picks otherwise when they are enrolled. The TAK server will not create an account with no channels, so leaving this empty means nobody can be added at all.
Loading…
Lock this console
Bring people in
Roster
Everyone in your agency, as the phone sees them.
Loading…
Add a person
Creates the account, the TAK login, and a one-time code to hand them. Their phone configures itself from it.
The mobile number is what the text and voice pager calls. Without it, that person can only be reached by push.
Send it is how their code reaches them. Left alone, it uses whatever contact details you filled in above — both if they have both, one if they have one, and nothing if they have neither, in which case you read them the code yourself. Pick Not at all when somebody is standing in front of you.
TAK app decides which setup file they get and which instructions are sent with it. An Android user handed the iPhone file cannot use it, so this one is worth getting right.
Pick a template to fill these in, or set each one. Read \u2192 = they see it. Write \u2190 = they share to it. Both \u2194 = two-way. The same words, arrows and colors Sentinel uses.
Loading…
TAK login is their username on the TAK server — the one they
sign in to the TAK server with. Left on auto it is worked out from
their name: first initial and surname, so Dana Ruiz becomes
druiz. Set it yourself when that name is already taken,
which is the case for anybody who had a TAK account before this system
— the TAK server refuses a duplicate outright.
For a dispatcher or an administrator who works this console and never carries a phone. They get a sign-in code and the screens their role allows. They get no TAK account, so the TAK app will have nothing to connect to. Do not use it for anybody going out.
Bulk enroll
Paste a spreadsheet, or choose a file. Copy the rows straight out of Excel or Google Sheets — including the header row.
What will happen
Each column below says how it will be read. Change any that are wrong — the preview updates as you do.
Import
Sent enrollments
Whether each person has opened their link. "Sent" for a long time usually means it never reached them — check the address or the number, then send a new one from the Roster.
Loading…
Add a file
A plugin, a new ATAK build, a map, a data package, an installer. Upload it here, then choose below whether everyone gets it or just one person.
Your files
Everyone can download puts a file in your agency's list, below — anyone signed in can fetch it themselves, with no link to make and nothing to expire. Or check one on the left and make a one-time link for somebody who has no account at all.
What your people see
Exactly what somebody signed in to your agency gets. This is the “Everyone can download” column above, from their side.
Loading…
Send some to one person
For somebody with no account and no app — they open a link and download it. Tick the files above first.
Links you have sent
"Opened" tells you it reached them. Cancel one and it stops working immediately — the file stays, and your other links keep working.
Packages
What a kind of person gets — SWAT, Patrol, Volunteer. Pick one when you enroll somebody instead of setting the same nine fields again. Agency default is the fallback for anyone with no package, and the base the others build on.
Loading…
New package
TAK channels adds to the agency default
Everyone on this package gets these as well as the agency's default channels, not instead of them. Read \u2192 = they see it. Write \u2190 = they share to it. Both \u2194 = two-way. The same words, arrows and colors Sentinel uses.
Picking a template fills the channels below with what the TAK server has for that group. You can still change any of them afterwards — the package stores the channels themselves, so editing the template at the server later does not reach back and change this package.
Loading…
Toolbar replaces the agency default
On the toolbar
In the overflow menu — click to add
Hidden tools
Tucked out of the way — off the toolbar and out of the overflow menu. Not taken away: they are still in the app's own toolbar settings, several taps deep. Nobody is ever stuck without something they turn out to need.
Click to hide
Files adds to the agency default
Files
The library. Upload once here, then choose who gets what in a package below. Everyone means it goes out with every enrollment; unchecked, only packages that name it carry it — the file stays either way.
Loading…
Who has picked it up
Phones check in when the app is opened, and every few minutes while it stays open. Nothing is pushed — a change reaches somebody the next time their app checks, which for a phone in a locker is whenever it comes out.
Loading…
Agency default
What everyone gets unless a package says otherwise. Phones already in the field do pick this up — they check in when the app is opened and every few minutes while it stays open, so a fix reaches somebody without re-enrolling them. Nothing is pushed, though: a phone in a locker gets it whenever it comes out. See Who has picked it up for who actually has.
Without it every ArcGIS basemap quietly falls back to a demo style, which looks like a broken map rather than a missing setting.
Toolbar
On the toolbar
In the overflow menu — click to add
Hidden tools
Tucked out of the way — off the toolbar and out of the overflow menu. Not taken away: they are still in the app's own toolbar settings, several taps deep. Nobody is ever stuck without something they turn out to need.
Click to hide
Group code
One code many people can use — for a class, a callout, or a mutual-aid group. Everyone who uses it gets the same settings.
Everyone who joins on this code is tagged with this. It was missing here entirely, so whole classes used to arrive belonging to nowhere while people added one at a time were tagged properly.
Joiners are numbered from it — VOL-01, VOL-02.
Left blank they are called VOL.
Read \u2192 = they see it. Write \u2190 = they share to it. Both \u2194 = two-way. The same words, arrows and colors Sentinel uses.
For a dispatcher or an administrator who works this console and never carries a phone. They get a sign-in code and the screens their role allows. They get no TAK account, so the TAK app will have nothing to connect to. Do not use it for anybody going out.
Video
Live feeds from the video server. Turning recording on or off changes what gets kept, so it needs the same permission as editing the roster.
Loading…
Where phones send video
Each agency has its own. Phones pick this up when they enroll, so nobody types an address or a password into a handset.
Loading…
Send an activation
A call-out: it goes by push immediately, then text, then a phone call, until someone answers — and the board below shows who has.
The app calls this an activation too, deliberately: one thing, one word, on every screen anybody sees.
Teams
A name for a group of people, so you can page them together instead of picking them one at a time — they appear in Who above. Nothing to do with TAK channels or team color.
Loading…