Credentials Storage For Teams
MapToPlay now lets teams save encrypted tokens and username/password pairs once, then reuse them when a workflow needs credentials.
Some map data providers need credentials. Sometimes it is a token, sometimes it is a username and password, and until now that usually meant pasting the same details again when a wizard or reprocessing action asked for them.
That works, but it is not the kind of thing you want to repeat while building maps. So MapToPlay now has team-level credentials storage.
Saved On The Team
Credentials live on the Teams page because that is where shared project work already happens. You can create a credential once, give it a clear name and description, and reuse it later without digging through notes or messages.
For the first version, there are two simple types: token, and username/password. They are intentionally generic, so this is not locked to one provider or one feature forever.
Built Into DTM
The first workflow using this is DTM. When a provider asks for credentials, you can enter them manually for one run, select an existing saved credential, or enter them manually and save them at the same time.
The same flow is available when reprocessing DTM, so rerunning terrain does not become another round of copy-paste.
- Create reusable team credentials from the Teams page
- Store tokens or username/password pairs
- Select saved credentials when a DTM provider asks for them
- Use manual credentials when you do not want to save anything
Small, But Useful
Saved credentials are encrypted, and the UI is deliberately boring: name it, store it, select it when something needs it.
This is not the loudest feature in the world, but it removes friction from real workflows. Less copy-paste, fewer interruptions, and a cleaner path through tools that need access to external data.
As always, I am looking forward to seeing where this makes people faster, and where it still needs more polish.
Stan, Developer of MapToPlay