People are at the center of Talentelly. Admins need a reliable way to find, invite, associate, and sometimes correct member records at scale via Users and user management. Individuals need an account that feels like their story—not a row someone else mis-typed in a sheet three years ago.
For admins: the essentials
- Open Users in the admin sidebar.
- Use search (name, ID, email—whatever your org indexes) to locate one person or to verify an import.
- Use manage flows to adjust entity associations, roles where the product supports them, and operational fields—always through guided screens so audit trails and validations stay intact.
Example: Lakshmi transferred from the morning batch to the evening batch at a coding bootcamp. The admin opens Users, finds her profile, updates the association to the new cohort entity or group—without creating a duplicate “Lakshmi K.” record that breaks certificates later.
When to use bulk upload vs one-by-one
| Situation | Approach |
|---|---|
| 10 new trialists after a weekend camp | Add or invite individually; faster than templating. |
| 400 freshmen on one sheet from the registrar | Bulk upload with the official template; fix validation in bulk. |
| Fixing 5 typos post-import | Users search + inline edit; re-uploading the whole file risks duplicates. |
Example: A state-level debate society receives a CSV from 12 schools. They run bulk upload, get 22 errors for malformed phone numbers, fix those rows in Excel, re-upload only the corrected file or rows per product flow, then assign everyone to Regional Round — North group. Details: bulk operations.
Large file jobs may also surface under bulk overview screens depending on your workflow.
For individuals: your side of the house
- Profile — photo, bio, instruments or positions, links you want public. This is the “resume header” for hub and shared certificates.
- Activity — a chronological view of what you joined, placed in, or completed—useful when someone asks “what have you done lately?”
- Entities — which organizations you are linked to; useful when you move cities or schools and need a clean paper trail.
- Settings & notifications — email/SMS/push preferences, password, and security—your control, not the entity’s.
Sign in from Account when you need any of the above.
Example: Arjun is applying for a summer theater program. He updates his profile headshot, checks that his public highlights show last year’s festival, and turns on notifications so he does not miss a callback event the entity publishes.
Why public profiles matter (real friction when ignored)
Many hub experiences and share links resolve to public profile fields (shared URLs typically look like /hub/profile/{id} once you open someone’s public page from discovery). If the name is wrong, the certificate says “A. Kumar” while the hub says “Arnav Kumar,” selectors and parents lose trust.
Example: A school prints merit certificates before students update profiles. Ceremony day photos look wrong on social because the hub still shows an old class label. Fix: nudge students to update profiles before batch certificate generation, or standardize naming at import time.
Coordination between admin and participant
Healthy programs split responsibility:
- Admins own roster truth (who is officially in the program)—groups, teams.
- Participants own presentation truth (how they want to be seen publicly).
Example: The admin ensures Sara is in Team U-14 Girls; Sara chooses whether to show “Midfielder” on her public profile and which past tournament to pin.
Tips
- After any big import, open three random profiles in the hub view and one edge case (hyphenated name, long school name) to catch systemic errors.
- Naming convention doc: One internal rule (“Always
Last, Firstin uploads”) saves dozens of duplicate-detection headaches. - Encourage self-service profile completion with a single Slack/WhatsApp template: “Please log in and confirm your name and photo before Friday’s certificate run.”
Related: Entity management · Security · Help and support