User roles in SchedEx: who can see and do what

TABLE OF CONTENTS

1. Introduction
2. The two things that decide your access
3. The four roles at a glance
4. Your relationship to an Exchange Agreement
5. Working with Exchange Agreements
6. Building what agreements use (setup)
7. Running transfers and handling files
8. Dashboards and reports
9. Administering a tenant
10. Platform administration
11. What any signed-in user can do
12. A few things to know
13. Related guides

Introduction

SchedEx decides what you can see and do from two things working together: your role, and your relationship to each Exchange Agreement. This guide explains both in plain terms, then walks through who can do what across the product — so you can tell at a glance what your account can do and who to ask when you need more.

The two things that decide your access

Every action in SchedEx is allowed only when both of these agree:

• Your role — one or more of Regular User, Setup Admin, Tenant Admin, System Admin. Your role gives you broad abilities (for example, "build connectors" or "manage users").
• Your relationship to the Exchange Agreement — whether you are a representative of one of its sides (or a contributor), and which side and direction you hold. This is what lets you act on a specific agreement.

That second part is why a Regular User can still sign, pause, run and view transfers — but only on the agreements they are a representative on.

An action is allowed only when both your role and your relationship to the agreement permit it.

The four roles at a glance

Roles are not a ladder — they are not hierarchical. Each role grants only its own set of abilities. A higher-sounding role does not include the others: holding System Admin does not give you Tenant Admin or Setup Admin powers, and a Tenant Admin is not automatically a Setup Admin. Someone who needs several areas is simply given more than one role.

The four roles are peers, each with its own area — you combine them for broader reach, you don't climb them.

Your relationship to an Exchange Agreement

Alongside your role, your standing on a specific agreement decides what you can do with it:

• Representative — a person named responsible on one side (owner or partner) of an agreement. Representatives can sign their side, pause/resume, run transfers, resolve conflicts, and upload/download files for that agreement.
• Contributor — someone from a different organization added to a same-organization agreement with a Send, Receive, or Both direction. See Contributor tenant.
• Sender / Receiver — the side and direction that governs who may run an upload versus a download.
• Tenant Admin elevation — a Tenant Admin is automatically treated as having representative-level authority over every agreement in their organization, even without being named on it.

Working with Exchange Agreements

Building what agreements use (setup)

Most "building" is Setup Admin work, within your own organization.

Running transfers and handling files

Running a transfer and moving files is governed per agreement — so a Regular User who is a representative can do most of it on their own agreements.

See Support logs for who can send a transfer's logs to the support team, and Managing files for the Files module.

Dashboards and reports

See SchedEx reports and Reading the Autonomous Component Dashboard.

Administering a tenant

These are Tenant Admin jobs, for your own organization. (A System Admin can also do the people-management ones across organizations.)

Platform administration

These are System Admin jobs, across the whole platform.

What any signed-in user can do

Regardless of role, every signed-in user can:

• View their own profile and in-app notifications, and set their notification preferences.
• View the term dictionary and create / use mapping formulas.
• Test a connector.
• See the simplified organization list (used when choosing a partner for an agreement).

A few things to know

• Roles are not hierarchical. They are independent sets of abilities, not levels — see The four roles at a glance. Broad reach comes from holding more than one role, not from one role "including" the others.
• The first user of a new organization becomes its Tenant Admin automatically. That person can then set up the organization and assign roles to everyone who follows.
• New users appear automatically the first time they sign in — there is no separate "invite" step. A Tenant Admin then assigns their role.
• A Tenant Admin controls roles within their own organization, but with limits: they can grant Regular User, Setup Admin or Tenant Admin, and enable or disable users — but they cannot grant System Admin, cannot change a System Admin user, and cannot touch users in another organization. Only a System Admin can grant System Admin.
• You can't change your own role. Ask a Tenant Admin (within your organization) or a System Admin.
• One account per organization. If you belong to two organizations you have a separate account in each; there is no "switch organization" button — you sign in against each one.
• Who to ask: a Tenant Admin for extra access within your organization; a System Admin for platform-level things and new organizations.

Related guides

• Contributor tenant — adding a third-party organization to an agreement as a Send/Receive contributor.
• Support logs — who can send logs to the support team.
• SchedEx reports — who can view reports and what they show.
• Glossary — shared SchedEx terms.