How to manage users manually

Dyknow's Users feature enables Dyknow Users with the Tech Coach or Administrator role to:

  • Manually create, edit, and archive Users;
  • Filter Users by School Name/Code and Role;
  • Sort and review Users by:
    • First Name;
    • Last Name;
    • School;
    • Role;
    • Last Date Communicated;
    • Version #; and,
    • Last Monitored Session.
  • Identify a user's Class assignments;
  • Identify student Users that have (not) been monitored recently and those who have never been monitored; and,
  • Identify Teachers who have (not) used Dyknow recently and those who have never used Dyknow.

This document is a resource for Dyknow Administrators to understand how to:

 

CREATE A USER

When a Dyknow User is needed, but this User does not exist in the district's Student Information System (SIS), manually creating a User is a great option. Follow the steps below to manually create a new User in Dyknow.

1. Click the gear icon DyKnow_Web_App_-_gear_icon__1_.png; you will be redirected to the Admin Settings.

2. Click the Users tab.

3. Click Create New User; the Create User modal will appear.

admin_settings_-_create_new_user.png

4. Complete the *Required fields on the Create User tab.

Note regarding SIS User IDs:

  • Include the SIS User ID field only if the User is included in your district's SIS and any existing data import files. Dyknow data imports match Users based on the SIS User ID field.

Note regarding student Users:

  • The Email Address field value must match the managed Google email address students use to login to their Chromebooks.
  • The Username field value must match the managed username students use to login to their Windows/PC, MacBook, or iPad.

5. Click Save.

 

EDIT A USER

Follow the steps below to manually edit an existing Dyknow User.

1. Click the gear icon DyKnow_Web_App_-_gear_icon__1_.png; you will be redirected to the Admin Settings.

2. Click the Users tab.

3. Search for the User (by name, username, or email address) and click the pencil icon to edit.

4. Edit the desired field(s).

Note regarding SIS User IDs:

  • Include the SIS User ID field only if the User is included in your district's SIS and any existing data import files. Dyknow data imports match Users based on the SIS User ID field.

Note regarding student Users:

  • The Email Address field value must match the managed Google email address students use to login to their Chromebooks.
  • The Username field value must match the managed username students use to login to their Windows/PC, MacBook, or iPad.

5. Click Save.

 

ARCHIVE A USER

Follow the steps below to manually archive an existing Dyknow User.

1. Click the gear icon DyKnow_Web_App_-_gear_icon__1_.png; you will be redirected to the Admin Settings.

2. Click the Users tab.

3. Search for the User (by name, username, or email address) and click the blue pencil icon to edit.

4. Set the User's Account Expiration Date to the desired expiration date, which must be less than today's date.

5. Click Save; the User will now appear in the Previous Users tab.

 

REVIEW USER DATA

Follow the steps below to review User data in Dyknow. 

1. Click the gear icon DyKnow_Web_App_-_gear_icon__1_.png; you will be redirected to the Admin Settings.

2. Click the Users tab.

3. Locate a specific User using a combination of Search, sorting column headers, and filtering by School and/or Role.

4. Click the expand button on any User to see more details, including:

  • Username
  • SIS User ID
  • Email Address
  • Hostname
  • IP Address
  • Account Expiration Date
  • Class assignments

admin_settings_-_current_users_2.png

Note:

  • If a Class is not hyperlinked, there is no SIS ID for that class, meaning it was likely created manually in Dyknow (instead of imported with other SIS data).
  • The Last Date Communicated and Version # columns are relevant for student users only and reflect the status of the installed Dyknow Cloud Connector.
Was this article helpful?
7 out of 14 found this helpful
Have more questions?
Submit a request

Comments

0 comments

Article is closed for comments.

Articles in this section

See more