Support

Support

Short answers, each with a link to more detail.

  • How do I identify something on a Lightning page?

    Hold Shift and move the pointer over a label, a field or a picklist value. You can change the key in Settings → On the Salesforce page, where Translate All has its own shortcut too. When Sextant cannot be sure which component a text belongs to, it shows nothing rather than guessing. 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. In that case 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. Sextant does not request tabs, the permission that makes Chrome say an extension can read your browsing history.

  • Sextant does not connect to my org

    Check three things, starting with the most common cause. In 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 in Lightning Experience, because Sextant does not run in Classic.

  • How do I report a security problem?

    Please report it privately, not in a public issue. The security policy explains how, what is in scope and what happens next.

Reporting a bug or asking a question

Write to support@usesextant.dev.

Or open an issue on the public repository: github.com/ManuelRP15/Sextant/issues

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