Clarity before claims.
Straight answers about professional ownership, evidence states, employer permissions, integrations, and product boundaries.
Does Credential Loom decide whether a course satisfies my license requirements?
No. Credential Loom is designed to organize evidence and compare activities with versioned requirement information. Final acceptance remains with the applicable licensing authority.
Who owns a professional's education history?
The professional owns their personal portfolio. An organization receives only the access the professional explicitly grants, and leaving an employer does not delete personal history.
Can one activity count toward more than one license?
The product architecture stores an activity once and can evaluate it against multiple license requirement sets. A qualification result is not the same as board acceptance.
Are provider integrations available today?
No automatic provider integrations are operational. Manual and guided document workflows are implemented locally, but real-customer uploads remain launch gated until malware scanning is tested. Each future provider connection requires authorization and a supported API before activation.
Should I upload patient information?
No. Credential Loom is not a clinical system. Do not upload patient records, diagnoses, treatment details, clinical notes, or other clinical information.
Can an employer see every certificate by default?
No. Employer access is designed to be explicit, granular, revocable, and auditable rather than automatic.
Still have a product question? Use the contact preview.
Keep your professional record ready for what comes next.
Start with one portfolio, then add the workflows your career or organization needs.