Gluon

Your own people over the last 30 days, those who asked nothing included. Tools are the searches and lookups their questions ran. The questions themselves are not shown here.

This is the instruction your brief is written from, and you can edit it directly. Say what it should lead with, what to leave out, which sections matter most to your organisation, and the tone. Reset puts the default back. Preview before saving, so nobody finds out at 06:00 what changed.

Gluon is not tied to any one system. A connector is a place it reads from: an Exchange or Microsoft 365 mailbox, an IMAP server, a Maildir, a folder of documents, a SharePoint site or a chat channel. Each connector files what it reads under a source of the same name. Credentials are encrypted and cannot be read back out, and nothing saves until the connection has been tested.

Items matching an active filter are never indexed, so they cannot appear in answers. Use it for traffic that carries no meaning: device telemetry, delivery-failure notices, automated feeds. Patterns use * and ?; anchor them (noreply.*) rather than wrapping in stars, or they catch more than you meant. Check what a pattern would catch before saving it.

A stop is a pattern on the question. A question that trips it gets the refusal text below instead of an answer, and the attempt is logged with the user. A few defaults for personal data about employees come with the product; you can retire them or add your own. Patterns are regular expressions, case-insensitive. Try a question before you save.

Tell Gluon who each sender's domain is: your own offices, customers, partners, authorities, suppliers, banks. One can hold several roles, and a machine that reports on itself is a system alert, kept out of the Overview. The brief and the answers use this to sort items by who wrote them. "Suggest roles" fills in what Gluon can already tell; it never overwrites what you have set.

Used to measure how fast you usually answer each counterpart, and who is waiting. In a chat your people are known by the names on their accounts.

The date on a digest and the days counted down to a deadline are that day where the readers are.

Each pattern is a regular expression with exactly one capture group for the number or code, e.g. \binvoice\s*#?\s*(\d{4,}). The label names the kind of reference; what the group captures becomes "Invoice 4411".

Removes the items this address wrote, takes the address off the To and Cc lines of everyone else's items, and drops the person from the register. Questions, answers, watches, drafts and summaries that name the address go too. Mentions inside other people's mail stay. One row is kept: the counts, who did it, when, and a mark made from the address, never the address.

Who the Overview leads with, who it leaves out, and which domains play which part. One address or domain per line.

What the indexer does at night for this organisation. Each change saves at once.

Every change made through the admin screens: who, when, what was called, and the names of the fields sent. Never the values. Newest first.

A role names the parts of this page a person may open. The built-in roles cannot change. A role somebody has cannot be deleted.

Shown on the sign-in page and in the bar, before and after sign-in. Leave a field blank to keep the product's own.

Name

Tagline

Accent colour Use it

Logo

Choose a file Remove

A PNG or an SVG. A PNG is shrunk to 256 pixels before it is saved.

Save Clear

An identity provider can make, change and close accounts here over SCIM. Give it the address below and a token. Making a token ends the one before it.

Plain search over titles, text and attachment names, on this machine. No AI, so nothing leaves. A dot marks what you have not opened. Press it to mark the item read.

These prompts reach every customer instance. Braces are filled in by the user when they run it: {source}, {days}, {period}, {sender}. Retire a prompt rather than deleting it once people have saved it.

Prompts users typed rather than took from the library, across every customer. A question that keeps being written by hand belongs in the catalogue. Rewrite it generically (swap the source for {source}) before adding it — these bodies are customer content.