Use Sourcing with care and authorization.

Permitted use#

Use Sourcing to manage approved sourcing programs, organize clients and projects, coordinate targets and assignments, review profile and QA decisions, administer authorized accounts, and maintain operational records for legitimate business purposes.

Account and access responsibilities#

• Use only your own account and the access assigned to your role.
• Protect passwords, tokens, device access, and extension credentials.
• Do not attempt to bypass authentication, alter authorization, or access records outside your permission.
• Report suspected compromise, mistaken access, data loss, or security incidents promptly.

Prohibited use#

• Do not access another person’s account or share account credentials.
• Do not probe, scan, stress-test, or attempt to exploit Sourcing or its production infrastructure without written authorization.
• Do not upload malware, destructive scripts, harmful content, or code intended to disrupt the service.
• Do not collect, store, export, or distribute personal, candidate, client, operational, or audit information beyond the approved workflow.
• Do not use Sourcing to violate applicable law, an applicable website’s terms, or an authorized organizational instruction.
• Do not use the extensions or APIs for scraping, surveillance, impersonation, spam, fraud, harassment, or unauthorized automated activity.
• Do not copy, disclose, sell, or transfer Sourcing credentials or records without authorization.

Responsible use of external websites#

When an extension or API is used with another website or service, use it only for an approved purpose and only with the access and information necessary for that purpose. Respect the website’s rules, consent requirements, access controls, and applicable law.

Responsible administration#

Administrators should grant the minimum access needed, remove inactive or unauthorized users, protect hosting and database credentials, review audit activity, keep extension packages current, and preserve records needed for security or compliance.

Reporting concerns#

If you identify a security weakness, privacy concern, incorrect access, or misuse of Sourcing, do not test it casually against production data. Stop the activity and report the concern through the Sourcing support page or the approved administrator or security contact.

Enforcement#

Access may be limited, suspended, or removed when necessary to protect users, information, service integrity, or legal and contractual obligations. Sourcing may preserve relevant records and investigate suspected violations in accordance with applicable requirements.

Questions#

If you are unsure whether an action is permitted, ask the Sourcing administrator or support contact before proceeding.