# Glossary

# Application

Applications are the basis for RemoteAuth. An Application is the representation of the external application connected to RemoteAuth. For example:

A developer has a SaaS called "Example SaaS". The developer would then create a new Application in RemoteAuth, called "Example SasS".

Applications are used to connect your Users to your: Roles & Permissions, Subscriptions, Notifications, etc.

# Application Members

Application Members are the relationship between a User and an Application. Applications are granted access to a User through an Application Member.

# OAuth Clients

Following the OAuth 2.0 protocol, OAuth Clients are the various implementations of your Application. For instance, you may have a web server and a mobile app that both make requests to RemoteAuth. Each of those implementations would get their own OAuth Client in RemoteAuth.

# Permission

Permissions are used to restrict specific functionality in your Application. Permissions belong to Roles. By granting a Role to a User, you also grant them all Permissions attached to the Role.

# Role

Roles are titles that can be given to your users. They are used to designate rank in your Application. Roles are also attached to Permissions.

# Team

Teams are used to group Users that belong to the same organization together. Teams are used as the owner for Applications.

# User

A User in RemoteAuth is both an end user of your application and of RemoteAuth. Users in RemoteAuth use one account across multiple applications. Read more about this under ApplicationMembers.