Skip to content

Brightspace launch users

A validated launch from Brightspace can create a user in Rowseta without an invitation or password. To find that user, open Settings > People.

Within your Organization, Rowseta recognises a launch user only by their Brightspace account as Brightspace signs it and the Brightspace site that signed the launch. Registering the tool again on that site keeps the same users. Email, display name and Brightspace user ID never identify, match or merge users. Two users can even share an email address. A different signed account or signing site creates a separate launch user. Each launch must still use a verified registration belonging to your Organization.

A launch user cannot use password sign-in or password reset.

A launch user’s first, last and display name follow the signed name information from Brightspace and refresh on each launch. If the launch supplies no name information, Rowseta keeps the stored name. This refresh does not change who the person is or their email. A role an administrator set in People is kept until an authorized administrator selects Use Brightspace role; a role assigned by a launch is determined again from the new launch. A supplied Brightspace user ID is also refreshed.

Active people with the built-in Owner or Admin role can edit someone else’s name in People when that person was invited or created at signup and has no Brightspace link. A launch-created administrator also needs a recorded ceiling lift. Names of Brightspace-linked or launch-created people cannot be edited there, nor can names of people created through single sign-on or with an unknown account origin. Follow Change someone’s name for the steps.

The signed Brightspace role determines the initial Rowseta role. Instructor, TeachingAssistant, ContentDeveloper and Administrator map to Instructor. Learner maps to Student. An empty role, an unknown role or Mentor maps to No Access. When a launch carries several roles, Rowseta uses the highest recognised one, so Instructor wins over Learner and an unrecognised role does not lower it. See the Brightspace LTI 1.3 roles table. A role set by hand in People remains in place on later launches until an authorized administrator selects Use Brightspace role.

The launch role still controls what opens: a Learner launch never opens the full app, even when the saved Rowseta role was raised. For widget details and student names, see the fixed rules and names on widget details rule. If you opened the link before this rule changed, open it again.

A launch-created user initially has access only within analytics, as their role and this launch allow. Reports, Insight widgets and Data can appear when that access allows them. Giving that user Organization access requires a recorded lift. A promoted person sees the same data as a directly signed-in user with that role in the full app. Other launch queries stay within the signed course. See fixed access rules.

The list shows Brightspace launch, registration status and Last active. The access label is Own widget numbers only for Students, Own course only for launch users whose assigned role cannot be promoted, and Depends on role and sharing for other assigned roles. It starts on recent launches, showing users active within 180 days. Choose All users under Users to find an older launch user. Open a user to see their Role, launch details and Last launch when recorded.

People with launch users showing Brightspace launch and Own course onlyOpen larger image

Select the user in Settings > People, then choose a new value under Role. The saved role survives later launches until an authorized administrator selects Use Brightspace role. If the control is unavailable, ask an administrator. The fixed rules explain role changes and the launch ceiling.

On a launch-created person’s People page, an administrator with Manage people can select Use Brightspace role after a manual assignment. If the person has access beyond Analytics, the administrator also needs Give Brightspace-launched people full access. This action is unavailable for yourself, an Owner, or someone who did not join through Brightspace.

Confirming gives the person No Access, signs them out of every device and removes any access beyond Analytics. Their next successful launch from Brightspace sets their role from fresh signed claims using the fixed mapping above. A suspended person stays suspended and must be unsuspended before their next successful launch. You can still assign a role manually in People afterwards.

To grant Organization access, select the user and choose the role under Role. Read the confirmation, type the role name and select Grant Organization powers. Rowseta records who approved the lift and when. Moving the user back to a role without Organization access restores the ceiling. See Roles and permissions for access rules and default grants.

If a launch says analytics is not available for this Organization, an Organization administrator can contact Rowseta support at support@rowseta.com. This refusal checks the Organization’s analytics availability setting.