This guide explains how to complete the Frontline Absence Management User Access Review form in Eduphoria Formspace. This review is part of the district’s bi-annual ITCG audit process and helps ensure that employee access to Frontline remains accurate and up to date for your campus or department.
This form is intended only for removing user access. It should not be used to request new access or modify existing permissions in Frontline.
Please complete and submit the form by the communicated deadline. The submission deadline for this review is May 22nd.
A completed form and all required file attachments must be included at the time of submission. Incomplete forms or submissions missing required attachments may be denied and returned for correction.
If you have specific questions or concerns, please reach out to lwistner@conroeisd.net.
Steps to Complete the Review
Follow the steps below to review and submit the Frontline user access form.
-
Open Eduphoria
-
Open Eduphoria by searching your Conroe ISD SSO.
-
Make sure you select the Eduphoria application and not Eduphoria Online Testing.
-
-
Open Formspace
-
Select Formspace from the Eduphoria homepage.
-
Open the Review tab.
-
Locate the form titled Frontline Absence Management User Access Review under Pending Review.
-
-
Review the User Access List
-
Open the attachment in the form to view the current list of personnel with Frontline Absence Management access for your campus or department.
-
Review the names to identify any employees who need to be removed (e.g., inactive staff, those who changed positions, or those who no longer require access).
-
Prepare your file for upload based on your review:
-
If you HAVE removals to request: Choose one of the following methods to document the changes:
-
Option A (Markup): Draw lines through, highlight directly onto the attached file, then save it.
-
Option B (Separate Document): Create a Word document listing the specific details of whose access needs to be removed.
-
-
If you HAVE NO changes (All access is correct): Simply save the original file to your computer. (Note: A file upload is required to complete the form, so you will upload this file in the following steps to confirm your review is complete).
-
-
Need help understanding Frontline permission levels or access types?
View the article: Frontline User Roles and Access Levels Explained
-
Confirm the Review Status
-
Select Yes if all listed access is correct.
-
Select No if changes are requested.
-
-
Upload the Required Attachment
-
A file must be uploaded to submit this form. Any submission without a file attachment will be rejected.
-
If you selected Yes above, upload the original attachment.
-
If you selected No, upload either:
-
your marked-up version of the original file
-
your Word document explaining the requested changes.
-
-
-
Submit the Form
-
To submit the form please select Continue Workflow at the top.
-
A comment box will open, you can add any notes there or just select Continue.
-
Frontline Approval: User Access & Profile Guide
Understanding how access is structured in Frontline is essential for maintaining security and operational efficiency. Access is determined by two primary User Types and further refined by four specific Profile Components.
1. Primary User Types
Every user is first categorized by their scope of authority:
-
Campus User: Access is restricted to viewing or modifying data at a specific campus or department.
-
Organization User: Access is granted at the district level, allowing for broader oversight across multiple locations.
2. Profile Components
Beyond the primary user type, four specific areas define a user’s experience and permissions:
-
Permission Profile: Defines what actions a user can take (e.g., Campus User, Department Approver, etc.).
-
School Visibility: Defines which locations (campuses or departments) the user is permitted to see.
-
Employee Type Visibility: Defines which categories of employees (e.g., Professional, Paraprofessional) the user can manage.
-
Absence Approver Profile: Defines the user’s specific Approval Level within the workflow.
3. Typical User Profiles
The following information illustrates common configurations used across the district: