Sharing

Keeping intel safe

SENTRY exists so Star Citizen players have a good place to write down what they saw, think about it, and share it with the people they trust. This page is not a military instruction. It is a handful of habits that keep that notebook useful.

The short version

Write what you saw. Share it with the smallest group that still helps your team. Remember that once a sentence leaves your screen, you no longer fully control it. SENTRY is built around that fact — private by default, chips for audience, personal tags and reputation that do not ride along with a shared note.

The point is not to scare you off. The point is that this is a better place to keep Star Citizen intel than a screenshot dump in Discord, a spreadsheet on a laptop, or a public forum post.

What SENTRY already does for you

  • Nothing is public by accident. Notes, contact reports, tags, and reputation stay with you until you pick an audience.
  • Audience is a list, not a shout. Dissemination chips (people, orgs, groups) are who can see that one item. There is no “post to the whole site” button.
  • Your personal score stays personal. Tags and reputation numbers do not go out with a shared note. You can still hide org tags and org reputation in Settings → Prefs.
  • Sign-in is NAVCOM. The website and overlay use the same login. Log out on a shared PC.
  • Public search is only public data. Citizen and org profiles from RSI are the open layer. Your intel is the private layer on top.
New note
Met in Grim HEX. Escorted us to the pad.
you+ add
Save note
  1. Empty extra chips means it stays with you (plus any defaults you set).
  2. Glance at the chips every time before Save — defaults can fill an org you forgot about.

The saying that still applies

Once you share something, you lose control of it. You do not know who takes a screenshot, who forwards a quote in Discord, or whose account gets borrowed. That is true of every chat app. SENTRY does not magically stop a trusted teammate from copying text. What it does is make the first hop deliberate: you chose those chips.

So share on purpose. Treat SENTRY as the place you process intel — write it, trim it, decide who needs it — not as a vault that can never leak.

Tips that actually help

  • Facts first, opinion labeled. “Two Cutlasses camping the pad” ages better than “they’re always pirates.” Future-you will thank you.
  • Smallest useful audience. A recon cell group beats “the whole org” for something still messy. You can share more later. You cannot unscreenshot.
  • No real-world secrets. Handles, ships, locations in the verse: yes. Passwords, emails, home addresses, account recovery: never.
  • Do not paste other people’s private chats unless they asked you to. A contact report about what you saw in space is enough.
  • Check chips, then save. Default dissemination is a convenience. It is also the easiest way to overshare on a hurried note.
  • Private groups for standing teams. A named list you reuse is less error-prone than retyping twelve handles every time.
  • Shared computer = log out. Overlay and website both stay signed in until you sign out.
  • If a handle looks wrong, look them up first. Mentions attach to SENTRY records. A typo can park a report on the wrong citizen.

What we expect of each other

Use the tool in good faith. Do not treat SENTRY as a public shame wall. Reputation is a reminder for you, not a verdict for the verse. Notes about people should be something you would still stand behind if the person eventually saw a screenshot — because someday, someone might.

If you run an org’s intel, prefer groups and org sources over blasting every member. If you only fly with a few people, you may never need more than “myself” plus one org chip. That is fine.

Where this lives in the product

  • Dissemination — who sees a note or report.
  • Groups — named audiences you reuse.
  • Settings — defaults, prefs, share groups, sign out.