Skip to content

User access management

Every account, from created to retired, under rules you wrote.

Sharetru is secure file transfer for regulated teams — Sharetru Commercial on the Core and Complete plans, Sharetru Federal for CUI and ITAR data. Its user access management controls each account from creation to removal, with eight system roles, access groups, MFA, SSH keys and, on Complete, SSO and per-user IP rules.

15-day free trial · Role groups, access groups, MFA and SSH keys on Core and Complete · SSO, per-user IP rules and dual authorization on Complete, and in the trial · Sharetru Federal: the FedRAMP Moderate authentication baseline, preset

SOC 2 Type II AttestedFIPS 140-2 / 140-3 validated encryptionTLS 1.3 on Sharetru Federal · TLS 1.2 on Sharetru CommercialMFA and SSH keys on every plan; SSO on CompleteEight system roles

The problem

A shared admin login is not an access policy

Most file-transfer tools give you one administrator role and one kind of user. So the managed service provider gets site admin, the auditor gets site admin, the batch job runs on somebody’s password, and the contractor who finished in March still has a login in October.

Three failure modes, one cause: the account does not carry the rules. A Sharetru account does.

See the life of an account
  1. Over-privileged admins

    Everyone who helps you gets the keys to everything

    The managed service provider, the IT contractor and the auditor all end up as site administrators, because there is no narrower role to give them — and every one of them can open a file.

    Narrowed by eight system roles — including an MSP Administrator without file access of its own and two read-only Auditor roles — and group managers whose rights stop at their own group.

  2. Right password, wrong place

    A valid credential works from anywhere

    A service account’s password lives in a script on a laptop. A partner’s login works from a country you do not do business in. The password was never the problem; where it was used was.

    Narrowed by country access for the whole site, per-user IP range rules on Complete, and SSH keys for the connections no person makes — the key proves the account; the address limits where it can connect from.

  3. The account nobody retired

    People leave. Their logins don’t.

    The contractor who finished in March still has a login. The batch job still authenticates with a key from two vendors ago. The links a former employee created still work, and nobody knows what they shared.

    Narrowed by automatic suspension after a set number of quiet days, one screen that lists every user, folder and permission, and share links you reassign before you delete the account.

The life of an account

How does Sharetru manage a user account from creation to removal?

Sharetru manages a user account through six stages — create, approve, authenticate, scope, review and retire — and each stage is a control an administrator sets, not a convention someone remembers. User access management in Sharetru is that whole sequence: who may create an account, who must approve it, how its owner proves who they are, what it can reach and from where, how you review it, and how it ends.

Below, one account goes through all six. The days and addresses are one site’s choices; the controls are the platform’s.

Claire Donnellyc.donnelly@yourcompany.com · one illustrative account

StatusPendingActiveSuspendedRetired

  1. 01 · Create

    Day 1

    Created, held pending

    • by j.alvarez (admin)
    • invite: sets own password
    • dual authorization: on
  2. 02 · Approve

    Day 1

    Approved

    • by m.chen (authorizer)
    • never the creator
    • status: active
  3. 03 · Authenticate

    Day 1

    Password + app

    • Sharetru’s own sign-in
    • password · site policy
    • authenticator enrolled
  4. 04 · Scope

    Day 1

    Role, group, rule

    • User Administrator
    • Finance · /AP · /Close
    • 198.51.100.0–255 · HTTPS
  5. 05 · Review

    Days 2–30

    One sign-in, one refusal

    • 198.51.100.7 · allowed
    • 203.0.113.9 · refused
    • outside the IP rule
    • day 30 · access review
  6. 06 · Retire

    90–120 days inactive

    Suspended and retired

    • suspended at 90 days
    • links → r.patel
    • 10 days’ notice given
    • deleted at 120 days
One account, start to finish, and every step a setting you own. Days and addresses are illustrative; the controls are real.

Build the roles before you move a single file — free for 15 days.Role groups, access groups, MFA and SSH keys are on Core and Complete; SSO, per-user IP rules and dual authorization come with Complete, and the trial includes them.

03 · Authenticate

How do users authenticate to Sharetru?

Users authenticate to Sharetru either through default site authentication — Sharetru’s own sign-in, built into the application, with a password under a policy you enforce, a one-time code by authenticator app, email or SMS, or an SSH key for SFTP and SCP — or through single sign-on over SAML 2.0 or OAuth with Microsoft Entra ID, Okta, Auth0, OneLogin or PingOne. The method is chosen per user, not per site.

Every account uses default site authentication unless you point it at your identity provider. So your staff can sign in through your directory while partners, auditors and service accounts stay on the default — and no outside identity ever has to enter your tenant.

  • Passwords, with rules that are enforced.

    Minimum length; upper, lower, numeral and symbol; expiry after a number of days you choose, with warning emails; a waiting period before a password can be reused; reset links that expire. Or switch off self-service edits and have administrators trigger every reset.

  • One-time codes by app, SMS or email.

    Enable OTP for the site, then per user, with only the methods you allow, and set how long a code lives. An administrator can reset a user’s MFA when a phone is lost. On Sharetru Federal, OTP is required, by authenticator app only.

  • SSH keys for the connections no person makes.

    Attach an RSA or ECDSA public key to a service account and switch it to key authentication for SFTP and SCP. Pair it with an IP rule: the key proves the account; the address limits where it can connect from. Our host keys are published under Site Identity, so your scripts can pin them.

Two kinds of people, one site

Your staff through your directory. Everyone else on default site authentication.

Default site authentication is the sign-in Sharetru itself provides: a username and password checked by Sharetru under your password policy, with a one-time code or an SSH key alongside it. Single sign-on hands that check to your identity provider instead. The choice is made on each user, not on the site — so partners, auditors and service accounts stay on the default and never need a seat in your tenant, and your tenant never sees them.

SSOYour staff → single sign-on
  1. Register Sharetru with your identity provider — Entra ID, Okta, Auth0, OneLogin or PingOne, over OAuth or SAML 2.0.
  2. Assign the app to the users or groups who should be able to sign in. Nobody else can.
  3. Each user also has a Sharetru account, with the directory name as the username and, optionally, pinned to its Entra Object ID. Your directory decides whether they can sign in; Sharetru decides what they can reach.
  4. They sign in through your directory. Every factor, MFA included, is your identity provider’s. Disable them there and they can no longer sign in through your directory; suspend the Sharetru account too, so it leaves your access review.
DefaultPartners and service accounts → default site authentication
  1. A Sharetru username and password under your policy — or invite the person to set their own first one.
  2. A one-time code by authenticator app, email or SMS. Or an SSH key for the batch job.
  3. Restrict the account to an address range, a protocol, or both.
  4. Grant folders by access group or one at a time. Nothing is inherited from your directory, because nothing in your directory was ever involved.

04 · Scope · role groups

What user roles does Sharetru have?

Sharetru has eight system role groups — Site Administrator, User Administrator, File Administrator, MSP Administrator, Site Auditor, Files Auditor, API User and New User Authorizer — plus group managers with user and file rights scoped to one access group.

Role groups are defined by the platform: they cannot be renamed or deleted, and they apply across the whole site. A user can hold more than one, and the privileges add up — so give an MSP or an auditor only that role. A user with no role group reaches only the folders they have been given permissions to, directly or through an access group. The definitions your assessor reads in our documentation are the ones running on your site.

Role groups · what each one can do

YesScoped — the cell says howNo

CapabilitySite adminUser adminFile adminMSP adminSite auditorFiles auditorGroup manager
Create, edit and delete users
YesYesNoYesNoNoOwn group
Reset passwords and MFA, set SSH keys and IP rules
YesYesNoYesNoNoOwn group
Configure site-wide settings
YesNoNoYesView onlyNoNo
Open, upload, download or delete files
YesNoYesNoNoNames onlyOwn group
View reports
AllUser reportsFile reportsAllAll, read-onlyNoOwn group

Two roles appear only when their feature is on: API Users once the API is enabled — and an API key never outruns the privileges of the user behind it — and New User Authorizer once dual authorization is on.

Read the role documentation
  • MSP Administrator: a Site Administrator without file access of its own.

    Built for the managed service provider — or the internal IT team — that you want running the site but not reading what is in it. They manage users, groups and settings and see the folder tree. A user whose only role is MSP Administrator cannot open files. Because the role can assign other roles, give it only to people you trust with that.

  • Site Auditor and Files Auditor: read-only, two scopes.

    A Site Auditor views site settings and the dashboard, users, groups and their permissions, every folder’s access, notification, retention and share settings, and all reports, but never a file name. A Files Auditor sees the name of every folder and file, to confirm what is stored and where, and cannot open, download or preview any of it. Give the assessor the role that fits the engagement and they look for themselves instead of asking you for screenshots.

  • New User Authorizer: the second signature.

    With dual authorization on, a new account waits in pending until an Authorizer approves it — and the Authorizer can never be the person who created it. Both the request and the decision go out by email.

04 · Scope · access groups

How do access groups and folder permissions work?

An access group is a set of users with common permissions to a set of folders: add a folder, choose whether its subfolders come with it, and check view, download, upload and delete for each. The same grants can be made for a single user, and every user can navigate the root without being able to upload, download or delete there.

Group managers get a slice of administration inside one group — the user rights, the file rights, or both — and nothing outside it. Link sharing is granted per user by an administrator, separately from folder access; guests who only ever send or receive by link never get a folder grant at all.

What a group controls

  • Folder list
  • Subfolders inherit
  • View
  • Download
  • Upload
  • Delete
  • Per-user grants too
  • Home directory

Manager · user rights

  • Create users
  • Edit users
  • Add existing users
  • Remove users
  • Authentication tab
  • IP restrictions
  • SSH keys
  • Reports · own group

Manager · file rights

  • Full file control
  • Notifications
  • Retention rules
  • View shares
  • Set folder permissions
  • Reports · own group
  • 8

    system role groups, defined by the platform and applied across the whole site

  • 14

    delegated manager rights, each scoped to one access group

  • 5

    identity providers over SAML 2.0 or OAuth — Entra ID, Okta, Auth0, OneLogin, PingOne

  • 1

    screen for every user, every folder and every permission — exported to CSV

04 · Scope · where a login may come from

Can I restrict where and how a user signs in?

Yes — by country for the whole site, by IP address range and protocol for each user, with as many rules per user as you need, and by email domain for anyone you let in through a share link. Every Sharetru site starts locked to the United States and you expand country access from there, on a commercial IP database updated weekly; per-user rules are checked after the login succeeds; the domain lists apply to every link anyone on your site sends.

Lock a batch account to one host and SFTP. Keep field staff on the web. Hold a finance user behind the corporate firewall. A rule you do not write allows any address over any active protocol — so write the rule. Per-user IP rules come with Complete.

Four rules we see on most regulated sites

Addresses are documentation ranges, not real ones

The accountAllowed fromAllowed protocolWhy
Clearinghouse batch jobservice account · SSH key

198.51.100.10

SFTP

The key proves the account; the address limits where it can connect from.

Payer integrationpartner system

203.0.113.0 – 203.0.113.255

SFTP

Their whole egress block, and only the protocol their system speaks.

Field staffpeople, on laptops

Any

HTTPS

Web only. No SFTP or FTPS client on a laptop, so nothing runs unattended.

Finance controllerone person, one rule

192.0.2.0 – 192.0.2.255

Any

From behind the corporate firewall or not at all. Rules are per user — write one on each account that needs it.

A user restricted away from HTTPS is refused at the web login with a generic error that explains nothing — by design, and the most common reason a restricted user calls you. Tell them first.

See the restriction examples
  • Country access, site-wide.

    Every site starts with the United States allowed; add the countries you work with and every active protocol honours the list. Switch it off for troubleshooting without clearing the list. On Sharetru Federal it stays on, with the United States always allowed, and the list only grows.

  • Default is open. On purpose.

    A new account with no rule may connect from any address over any active protocol, so you are never locked out by accident. Restriction is a decision you make per account — and if you do lock yourself out, support can let you back in.

Guests · provisioned by a link, inside your rules

How does a guest user get into my site, and what can they reach?

A guest can exist only because one of your registered users sent them a Sharetru link — there is no way to register for your site from the outside — and a link can only go to an email domain your administrator’s allow-list or block-list permits. The recipient registers once, with the address the link was sent to, a password they set and a second factor when your site requires one; from then on they open only what has been shared to them and send files in only through a drop-off link into a folder you chose. A guest never browses the site, never holds a folder grant, never connects over SFTP or the API, and never counts against your plan.

So a guest is provisioned — just not by hand. The administrator decides which registered users may send links and which domains may receive them; a registered user’s send is the invitation; the domain list is checked when the link is sent and again when the guest signs in; MFA is a site policy. When a short engagement becomes a long one, an administrator converts the guest to a registered user, with no second account to create.

How a guest comes to exist

  • A registered user sends a link
  • Link sharing granted per user by an admin
  • Domain allow- or block-list
  • Checked at send and at sign-in
  • Registers once with that address
  • MFA when you require it
  • No self-registration

What a guest can do

  • Open files shared to them
  • View or download, as the link allows
  • Upload through a drop-off link
  • Sign in with email, password and MFA
  • Within the link’s lifetime and uses

What a guest never gets

  • Browsing the site
  • A folder grant
  • SFTP, FTPS or the API
  • A seat on your plan
  • A way in without a link
  • Nobody registers from the outside.

    Every guest starts with one of your registered users sending a link — a right you grant per user — and only to a domain your allow-list or block-list permits, checked when the link is sent and again when the guest signs in. The guest then signs in with that address, a password set once and MFA when you require it, so a forwarded copy opens for no one. No link, no guest.

  • Convert when the relationship grows.

    An administrator can turn a guest into a registered user at any time, with no second account to create. From then on they sign in to the site, hold folder grants, connect over SFTP or the API — and count toward your plan like anyone else.

05–06 · Review and retire

How do I review who has access, and remove it when someone leaves?

Review access from the Users Access screen, which lists every user, every folder and every permission on one page, and from the Users, Access, Logins by Protocol and User Agreement reports — each with an Export CSV button. Remove access by suspending or deleting the account, or let inactivity suspend it for you. Reassign share links first; for SSO users, disable them in your directory and suspend the account here, so it leaves the review too.

Give the assessor the Site Auditor role and they can read all of it themselves, on your site, without a screenshot from you.

What you export

  • Users Access
  • Users report
  • Access report
  • Logins by Protocol
  • User Agreement
  • Export CSV

What the review answers

  • Who exists
  • Who is still pending
  • What they can reach
  • How they sign in
  • When they last did
  • What they agreed to

How access ends

  • Suspend
  • Auto-suspend after inactivity
  • Reassign share links
  • Delete
  • Disable in your IdP, then suspend
  • The access review on one screen.

    Users Access shows every user, every folder and every permission, read-only, with a username link to fix the one that is wrong. Export it, hand it to the assessor, done.

  • Nothing leaves with the employee.

    Reassign the share links they created to a colleague, then suspend or delete the account. Recipients notice nothing; the folders stay where they were. On Federal, a suspended account is removed within 30 days, with at least ten days’ notice.

Choose your platform

Sharetru Commercial or Sharetru Federal?

Sharetru Commercial and Sharetru Federal share the same roles, groups, SSO, SSH keys and restrictions; on Commercial every authentication setting is yours to choose, while Federal arrives with the FedRAMP Moderate baseline preset and lets you tighten from there. Choose Federal for CUI and ITAR data, Commercial for regulated commercial data. Both are administered by Sharetru’s U.S.-citizen staff, in U.S. data centers.

Sharetru Commercial

Regulated commercial data

For healthcare, financial services, manufacturing, engineering and professional-services teams giving partners, auditors and service accounts a governed way in under HIPAA, SOC 2, GLBA/SOX/PCI or GDPR.

  • MFA by authenticator app, email or SMS — optional, enabled per site and assigned per user
  • FIPS 140-2 validated cryptography
  • SSO over SAML 2.0 or OAuth with Entra ID, Okta, Auth0, OneLogin and PingOne
  • Eight role groups, access groups (five on Core, unlimited on Complete), scoped group managers
  • SSH keys and country access included; per-user IP restrictions and dual authorization come with Complete
  • Every sign-in setting is yours — lockout, inactivity, expiry, re-use; 15-day free trial
Sharetru Federal

CUI, ITAR and the defense industrial base

For contractors, primes and agencies that need every person who signs in with Sharetru’s own sign-in — staff, partner or guest — behind a second factor a C3PAO can verify, on a service a C3PAO can verify too.

  • FedRAMP Rev 5 (Class C) Certified IaaS, PaaS and SaaS — the same roles, groups, SSO and SSH keys
  • FIPS 140-3 validated cryptography
  • MFA required, authenticator app only — no email or SMS codes; five-minute codes; guests included
  • Baseline preset: three failed attempts locks for an hour; expiry within 90 days; no re-use for 90 days or five changes
  • Inactive accounts suspended within 90 days and removed within 30 more; the United States always allowed
  • U.S.-citizen staff, U.S. soil — administered only by U.S.-citizen staff, who are U.S. persons as ITAR defines them (22 CFR 120.62); data stays in the United States

FAQ

Questions teams ask before they hand out a login

Accounts and roles

Does Sharetru have three roles — Administrator, Team Manager and User?

No. Sharetru has eight system role groups plus group managers scoped to one access group; the three-role description came from an earlier version of this page. Team Managers are a legacy structure that the Groups system replaced, and sites still using them should migrate to access groups with group managers.

Can an MSP or an auditor manage or inspect my site without seeing my files?

Yes. A user whose only role is MSP Administrator manages users, groups and settings and sees the folder tree, but cannot open files. Because the role can assign other roles, give it only to people you trust with that.

The two Auditor roles are read-only everywhere: a Site Auditor sees settings, users, permissions and reports but no file names; a Files Auditor sees folder and file names but cannot open, download or preview a file. Privileges add up across roles, so give an MSP or an auditor only that role.

Can one user hold more than one role?

Yes — a user may belong to several role groups at once, and the privileges add up. So give an MSP or an auditor only that role: a user who holds either one together with File Administrator can open files.

Is there a second approval for new accounts?

Yes, on Complete — with dual authorization on, a new account is held as pending until a New User Authorizer approves it, and the Authorizer can never be the person who created it. Both the request and the decision are emailed.

How do I add many users at once?

Import a CSV: Sharetru gives you a sample template, checks every row and shows a row-by-row error report before anything is committed. With invitations on, each new user receives a link and chooses their own first password; with dual authorization on, each one still waits for approval.

What happens after repeated failed logins?

The account lockout policy locks both the username and the source IP address at the limits you define; on Sharetru Federal, three failed attempts within fifteen minutes locks the account for sixty minutes. Current lockouts sit in one table where an administrator can inspect the details and clear them.

Authentication

What is default site authentication?

Default site authentication is Sharetru’s native sign-in, built into the application: a username and password checked by Sharetru under your password policy, with a one-time code by authenticator app, email or SMS, or an SSH key for SFTP and SCP. Every account uses it unless you assign the account to an identity service for single sign-on — and it is what partners, auditors and service accounts keep when your staff move to SSO.

Does Sharetru support single sign-on, and with which providers?

Yes — on the Complete plan, over SAML 2.0 or OAuth, with documented setup for Microsoft Entra ID, Okta, Auth0, OneLogin and PingOne. It is chosen per user, so staff can sign in through your directory while partners and service accounts stay on default site authentication. Each SSO user still exists as a Sharetru account with its own folder grants: your directory decides whether they can log in, Sharetru decides what they can reach.

Does Sharetru’s MFA apply to SSO users?

No. When a user authenticates through your identity provider, every factor — MFA included — is your identity provider’s, and no part of Sharetru’s own sign-in is used. Sharetru’s one-time codes apply to accounts on default site authentication.

Can a service account sign in without a password?

Yes — attach an SSH public key (RSA or ECDSA) to the account and switch it to key authentication for SFTP and SCP. Add an IP rule: the key proves the account, and the address limits where it can connect from. Sharetru’s host keys are published under Site Identity so your scripts can pin them.

What does Sharetru Federal preset for authentication?

Sharetru Federal arrives with the FedRAMP Moderate baseline preset: MFA required by authenticator app only with five-minute codes; account lockout after three failed attempts in fifteen minutes, for sixty minutes; password expiry within 90 days and no re-use for 90 days or five changes; inactive accounts suspended within 90 days and removed within 30 more, with at least ten days’ notice; country access on with the United States always allowed; a system-use announcement at sign-in; and personal data masked in the interface.

Can I change the Federal presets?

You can tighten them, and you can add countries; you cannot loosen anything else. Every Sharetru site starts locked to the United States, so adding a country is expanding country access, and that is yours to do on Federal as on Commercial. Beyond that: suspend inactive accounts sooner than 90 days, expire passwords sooner, require more than the baseline — but SMS and email codes stay off, the announcement stays on, and the ceilings stay where FedRAMP put them.

Restrictions, guests and plans

Can I control which email domains a share link may go to?

Yes — a site-level allow-list or block-list of email domains decides where links may be sent, for every link anyone on your site creates, checked when the link is sent and again when the guest signs in. It is an access control on the people you let in by link, separate from folder permissions and from the per-user IP rules.

Who can delete a file?

Anyone you have given the delete flag on that folder — plus site administrators, file administrators, and group managers with file rights inside their own folders. Sharetru does not keep prior versions of a file, and we will not tell you otherwise.

How does someone become a guest on my site?

Only by receiving a Sharetru link from one of your registered users — there is no self-registration — and only if their email domain passes your allow-list or block-list, which Sharetru checks when the link is sent and again when the guest signs in. Link sharing itself is granted per user by an administrator, so you decide who may send as well as who may receive. The recipient then registers once with that address, a password and MFA when you require it.

Can a guest become a registered user?

Yes — an administrator can convert a guest to a registered user at any time, with no second account to create. As a registered user they sign in to your site, hold folder grants, connect over the web app, SFTP or the API, and count toward your plan.

Is all of this on every plan?

Role groups, access groups, MFA, SSH keys, password strength and expiration, and country access are included on Core and Complete; Core includes five custom access groups and Complete unlimited. SSO, per-user IP restrictions and dual authorization for new accounts come with Complete. The 15-day free trial of Sharetru Commercial includes all of it. Sharetru Federal is an add-on to Core or Complete; SSO, per-user IP rules and dual authorization still need Complete.

Is Sharetru FedRAMP authorized?

Yes: Sharetru Federal is FedRAMP Rev 5 (Class C) Certified (the new name for FedRAMP Moderate), the status FedRAMP formerly called “Authorized”. It is the certified SaaS inside MIS Sciences Corporation’s GovPoint Cloud Services, package F1311222650 (Class C, Moderate), and FedRAMP maintains the listing on the FedRAMP Marketplace. Sharetru Commercial is not part of the package.

Get started

Build the roles in the trial — or let us build them with you.

Every new Sharetru Commercial signup includes a 15-day free trial with role groups, access groups, MFA, SSO, SSH keys, per-user IP rules and dual authorization included. Prefer a walkthrough? Bring your access-control questionnaire and we will answer it on a live Sharetru site, setting by setting.

Bring your access-control questionnaire to a 30-minute security and compliance review, or read the user guides first. Not a compliance project? Talk through how you move files today.

Sources. Details on this page are drawn from the Sharetru Knowledge Base (User Settings, Groups, Sitewide Settings, Single Sign-On Integration and Reports), the Sharetru Federal baseline configuration, and the Sharetru plan comparison.