Understanding The Access Level
v2026.4 · Updated 04 Oct 2026 · 2 min read
Before you start
Where you do this
Mail → Mail Basics
You will need
Nothing — this is background reading
Takes about
Two minutes
Understanding mail access levels
Like documents, Mail in SasCon is governed by organization-level access rather than individual recipients alone. Who can see a given mail — and the whole thread it belongs to — depends on which organizations have sent or received it.
Access rules for mail
- A user can view and act on a Mail only if their organization either sent it or received it — as a direct recipient in To, or in CC.
- Once any user in an organization has access to a mail, every user in that organization gains access to the whole thread by default — not just the specific person who was addressed.
- A new organization can be brought into an existing conversation simply by replying or forwarding the mail and adding users from that organization into To or CC. This works even for organizations that had no part in the original mail.
- Access applies to the entire mail thread, not just the individual message — once your organization is in, you can see every reply and forward in that thread, including ones sent before your organization was added.
How this shows up in the Mail list
The Mail list makes the organization-level nature of access explicit — alongside the usual From/To/CC columns (individual users), it also tracks access at the organization level directly:
| Field | Required | What to enter |
|---|---|---|
| From | Yes | The individual user who sent the mail |
| To | Yes | The individual recipient(s) |
| CC | Yes | Any individual users copied on the mail |
| From Organization | Yes | The organization that sent the mail |
| To Organizations | Yes | The organization(s) of every "To" recipient |
| CC Organizations | Yes | The organization(s) of every "CC" recipient |
The presence of dedicated From Organization, To Organizations, and CC Organizations columns confirms that SasCon tracks mail access at the organization level as a first-class concept — not just something that happens to fall out of who's listed as a recipient.
Document attachments follow their own access rules
A document attached to a mail doesn't inherit the mail's access rules wholesale — it keeps its own. For a standard document, sending it via mail to a new organization is exactly what grants that organization access to the document itself (see Sharing / Transmitting a Document). For a confidential document, mail access to the thread does not override its locked viewer list — recipients outside that list still can't open it, even though they're part of the mail thread. See Confidential Documents and Understanding the Access Level (Document Basics) for the full rules.
What you can see on a mail you have access to
- Mail Details tab: From, To (with a "Show all (N)" control and a "+N more recipients" summary when there are several), CC, Date Sent, Type & Status badges (e.g. Transmittal / Replied), Project, a Documents count, and the message body.
- Mail Thread tab: the full conversation history for that mail.
- Action buttons available: Mark As Closed Out, Reply, Forward.
Role Mail access SuperAdmin -Manage mail metadata across every organization and project Admin -View mail metadata across their own organization's projects Uploader -Same mail access as Viewer (no additional mail permissions) Viewer -Create, send, and view project Mail to other users
You need one of these roles:Viewing mail your organization has access to requires only the Viewer role or higher, and project access.
Related articles
Was this article helpful?
Version 2026.4 · Last reviewed 04 Oct 2026 by the SasCon documentation team