How Heart Spark Protects Intern Identity and Access
An applicant and intern guide to authenticated identity, separate Hub and ATS pathways, permanent role matching, protected evidence, access status, and audit accountability.
DIRECT ANSWER
In brief
Heart Spark combines authenticated account identity with separate protected password pathways for the Intern Welcome Hub and ATS. Server-enforced access rules connect each person only to authorized records and roles. Historical application email matching supports identity reconciliation, while profile evidence, continuation status, role-based administration, protected uploads, signed sessions, and audit records support accountability.
KEY TAKEAWAYS
What to remember
- Use only your own authenticated account.
- The Hub and ATS use separate protected password pathways.
- Historical emails support matching but never require passwords or inbox access.
- Private uploads and ATS responses remain behind authenticated routes.
- Access status and administrative actions are recorded for accountability.
Identity protection is not one screen or one password. It is a layered relationship among the authenticated person, the program pathway entered, the permanent role and evidence record, the current access state, and the server rules that decide which information can be viewed or changed.
Why are authentication and the program password both used?
Authentication identifies the account entering the Site. The program password selects the authorized Hub or ATS pathway. After entry, the signed-in identity and assigned permissions determine which personal, applicant, reviewer, or administrative records are available.
Why are the Hub and ATS separate?
The Hub supports onboarding, profile, learning, community, reflection, letters, guidance, and administration. The ATS supports applications, audiovisual interview consent, recordings, transcripts, review, and pipeline activity. Separate pathways reduce accidental mixing of applicant and participant functions.
How are people matched across different emails?
The intern records school and personal addresses previously used for relevant applications. An administrator may associate one of those addresses with the authoritative role assignment. The platform matches the normalized address without requesting the email password, inbox, or security code.
How are uploads protected?
Handshake evidence and professional headshots use authenticated upload and retrieval routes. The intern can access the person’s own files, and authorized administrators can review required evidence. General public journal visitors and ordinary community content do not receive access to those records.
How do roles limit access?
Applicants, interns, reviewers, mentors, administrators, and owners receive different capabilities. Administrative controls remain separate from public presentation. A permanent primary role is not the same as an administrative permission level.
How does continuation status affect access?
The Hub evaluates permanent role acknowledgment, monthly continuation due dates, and administrator suspension. Connected intern Sites can consult the authoritative status. The rules are enforced by protected server routes rather than relying only on a hidden button in the browser.
What do audit records contribute?
Significant profile, access, role, continuation, upload, ATS, review, and administrative actions can create dated audit events. These records support accountability, troubleshooting, and review while remaining protected from ordinary public access.
What responsibilities remain with the user?
Keep passwords and security codes private, use only personal authorized accounts, sign out on shared devices, review screenshots before upload, report unexpected identity or access behavior promptly, and avoid copying protected records into unapproved systems.
FREQUENTLY ASKED QUESTIONS
Questions and direct answers
Does Heart Spark ask for an email password to match historical addresses?
No. The platform uses the address text and never needs the email password or inbox access.
Are the Intern Hub and ATS the same protected pathway?
No. They use separate program password pathways and serve different functions.
Can a public journal reader see intern profile uploads?
No. Profile evidence is retrieved through authenticated, authorized routes.
Are access decisions enforced only by the interface?
No. Protected server routes enforce identity, role, and access requirements.