Brightspace Data Sets for Sessions and System Access do not depend on specific tools being turned on.
Entity Relationship Diagram
The following diagram shows the relationships between entities used to create Brightspace Data Sets for Sessions and System Access. To enlarge the diagram, right-click on the image and select Open image in a new tab.
Session History
The Session History Brightspace Data Set returns a list of login session histories for all users in your organization. Does not include app usage.
The Session History Brightspace Data Set contains data from 1 January 2021 onwards and adheres to the default system limit of 150 million rows of the most recent data.
Version History
|
Field
|
Description
|
Type
|
Size
|
Key
|
|---|
| 7.19 / 8.5 - Updated type |
SessionId
|
Unique session identifier.
Field can be null.
|
bigint
|
8
|
|
| 1.0 |
OrgId
|
Unique org unit Identifier.
Field can be null.
|
int
|
4
|
|
| 1.0 |
UserId
|
Unique user identifier.
Field can be null.
|
int
|
4
|
FK
|
| 1.0 |
DateStarted
|
Session start date time (UTC).
Field can be null.
|
datetime2
|
8
|
|
| 1.0 |
DateEnded
|
Session end date time (UTC).
|
datetime2
|
8
|
|
| 1.0 |
LastAccessed
|
Last access date time (UTC).
Field can be null.
|
datetime2
|
8
|
|
| 1.0 |
TimedOut
|
If session timed out.
|
bit
|
1
|
|
| 1.6 |
HistoryID |
Unique session history identifier. |
bigint |
8 |
PK |
System Access Log
The System Access Log Brightspace Data Set captures each time a user accesses the system from the LMS via a browser (Brightspace), from the Pulse app (Pulse), or from the Brightspace Parent & Guardian mobile app (BPG-mobile). System access using Brightspace Parent & Guardian is represented in the data set twice: one where Source=Brightspace and one where Source=BPG-mobile.
System access begins when the user logs in, returns after 30 minutes of inactivity, or opens the app. System access ends after 30 minutes of inactivity.
|
Note: In the differential for this data set, it's normal to see system access from the Pulse app with timestamps that fall outside the standard 24-hour window. This is because Pulse can't send system access events to the database when the user closes the app; it must send them the next time the user opens the app. If a user opened the Pulse app one week ago, then opens it again today, today's differential includes data with timestamps from one week ago.
|
Data from Brightspace and Pulse is available from September 2020 onwards. Data from Brightspace Parent & Guardian is only available from May 2022 onwards.
Version History
|
Field
|
Description
|
Type
|
Size
|
Key
|
|---|
| 5.6 |
SessionId |
Unique identifier for the session. |
nvarchar |
36 |
PK |
| 5.6 |
UserId |
Unique identifier for the user. |
int |
4 |
PK, FK |
| 5.6 |
Timestamp |
Date and time in which the system access changed state. |
datetime2 |
8 |
PK |
| 5.6 |
State |
Indicates whether a system access started or ended at the reported time. |
nvarchar |
20 |
PK |
| 7.6 - Updated description |
Source |
Source of the system access.
Possible values:
|
nvarchar |
20 |
|
| 5.6 |
AppVersion |
Version of the app, where applicable.
Field will be null for Brightspace sources.
|
nvarchar |
20 |
|
|
5.7 / 6.0 - Updated column size
|
Device |
Device used in the system access.
Field will be null for Brightspace sources.
|
nvarchar |
50 |
|
| 5.6 |
IsOfflineMode |
Indicates if a portion or all of the system access occurred offline with no internet connection.
Field will be null for Brightspace sources.
|
bit |
1 |
|
| 5.6 |
IPAddress |
IP Address at which the event occurred.
Field can be null.
|
nvarchar |
45 |
|