1. Docs
  2. Where signing in takes you

Where signing in takes you

Canopy has two applications you can sign in to, and one sign-in form. What you hold decides which one you arrive in, and occasionally you are asked to choose.

Overview

After a successful sign-in, Canopy asks what you can actually reach and sends you there. The answer comes from what you hold, never from being a member of the account. Someone whose membership is active but whose administrator grant has been revoked reaches neither application, and is told so on a page of its own rather than being dropped somewhere empty.

Being a member of an account grants nothing. Authority comes from a role someone granted you, and it can be taken away without your membership changing.

Two questions decide it

The destination is decided by two independent questions. The first has two answers, the second has three.

Can you open the Developer Console? You either hold Console admission or you do not.What is your access to the Admin Workspace? Operational, if you have a live assignment in an environment. Account-wide, if you hold an account-scoped role such as billing or the administrator roster, or if you own the account. Or none.The two are unrelated. Holding one says nothing about holding the other.

Every shape, and where it lands

Six combinations are possible, and each has one destination.

What you hold Where you land
Console admission only, the usual shape for a developer The Developer Console
An assignment in an environment, and no Console admission The Admin Workspace, on your responsibility screen
Both of those A short page asking which one you want
An account-scoped role such as billing, and no Console admission The Admin Workspace, on its account area
Ownership of the account, which includes Console admission The Developer Console
An active membership and no live grant A page explaining that you hold nothing here

Three things that surprise people

Console admission is not authority in the Workspace. It opens the Console and nothing else, which is why a developer is never offered a door into an account area with nothing in it for them.An owner lands in the Console, despite holding every account capability. Only operational authority in an environment is ever weighed against the Console; account-wide authority is reached afterwards through the application switcher.The choice appears only when you hold both halves. A developer with no assignment is never asked, an environment administrator without Console admission is never asked, and neither is an owner.

Next Step

Arrived in the Workspace? Your responsibility explains the screen you are looking at and how to read your own authority off it.

Environment
API version
v1.0
On this page Was this page helpful?

Tell us how we can improve this guide.