Staff roles

Portal users

A portal user is a person in your organization who can sign in at rubysig.com and manage the account. Portal users are separate from the mailboxes in your directory: a directory user gets a signature; a portal user runs the program. Portal users are not billed.

Today every portal user is an administrator of the companies they belong to. That means they can:

• design templates and banners, and make them live,
• read the directory and set per-mailbox address lines and aliases,
• see the company's connection values (relay address, DKIM records) on the Setup page,
• see billing — terms, invoices, amount due.

Access is per company. An organization with several companies (brands) shows a company selector at the top of the portal; a portal user sees only the companies they have been added to.

Adding and removing portal users

Portal users are added and removed by RubySig on request from an existing administrator, or during onboarding. Removing a person from the portal does not affect their mailbox or its signature — those come from your directory.

Note: The person who requested access for your organization is its first administrator. There is no self-service sign-up, by design: every portal user for a customer is one an existing administrator asked for.

RubySig staff

People who work at RubySig have their own, separate roles inside the RubySig console — owner, admin, sales, accounting, reader and so on — with capabilities such as setting prices, issuing invoices, and admitting new tenants gated by role. Those roles never grant access to a customer's mail; the relay does not keep mail, and RubySig staff can see only the configuration and billing data needed to run the service. The Data Processing Agreement sets out what that data is.

Coming

Finer-grained customer roles — for example a designer who can edit templates but not see billing — are on the roadmap. If you need that separation today, tell us how you would use it; that shapes what gets built.