Support

Support

Short answers, each with the place that says more.

  • How do I identify something on a Lightning page?

    Hold Shift and move the pointer over a label, a field or a picklist value. The key is yours to change in Settings → On the Salesforce page, where Translate All has its own shortcut too. If Sextant cannot identify a string with confidence it says Unknown origin; it never offers a list of guesses.

  • How does Activity know who changed something?

    It only says what it has evidence for: a change it observed between two reads, a change Sextant made itself, or an author and a date Salesforce reports. Salesforce records neither for a translation, so a translation change has no author unless Sextant made it — and Activity says Unknown rather than guess.

  • Where is my data stored?

    In chrome.storage.local, in your browser profile, on your computer: your settings, a cache of the metadata Sextant has read, the changes it observed, translation snapshots and your Workspace. Nothing is synced to a Google account, and there is no Sextant server to send it to. Settings → Privacy & security shows how much each kind uses, exports it and deletes it; uninstalling removes all of it.

  • Why does Sextant need each permission?

    Each one is listed with what it is for and what it does not do. The one that makes Chrome say read your browsing history — tabs — is not requested.

  • Sextant does not connect to my org

    Three things to check, in the order they usually explain it: Setup → Session Settings → Lock sessions to the domain in which they were first used must be off, or Salesforce rejects the background process's session; your user needs API Enabled; and the page must be Lightning Experience — Sextant does not run in Classic.

  • How do I report a security problem?

    Privately, please — not in a public issue. The security policy says how, what is in scope, and what happens next.

Reporting a bug or asking a question

Write to support@usesextant.dev.

Security reports go to the private channel in the security policy, never to a public issue.