Working with other services.

Open the instructions. Check the result after completing each step.

Training should lead to evidence.

Pulsar organizes requirements and training needs. Zmianowo/CrewShift is a separate application for delivering training and acknowledgements. Check access and connection scope for your organization.

Open module collaboration instructions

After connecting the services, check the result in both applications.

Last updated:

Access and data exchange scope

The application interface supports user workflows and communication with the organization’s data area. It is not a public integration API for external systems. The current scope does not provide API keys or webhooks for self-service ERP, HR, SharePoint or Google Drive connections. Keep documents and evidence in your organization’s area; an external file link does not replace an approved evidence version.

Controlled CSV, XLSX and JSON import and export are the primary data exchange methods. Available operations determine the format. Check export scope and permissions before preparing material; permission to view a record does not necessarily include permission to export it.

The Pulsar → CrewShift → Pulsar workflow

  1. In Pulsar, select the requirement, document change or action that creates a training, test or acknowledgement need. Check the source version and responsible person.
  2. Define participants and the expected evidence. Check CrewShift activation and participant access within the same organization.
  3. Complete the training, test or acknowledgement in CrewShift. Record the result, date and version of the material involved.
  4. An authorized person reviews and approves the result. In Pulsar, check that the returned evidence links to the correct requirement, control or action. Completion status alone does not replace effectiveness assessment.

Prepare and check an import

  1. Select the organization and record scope. Agree the data source, owner and rights to use the documents.
  2. Prepare the file in the format supported by the operation. Preserve identifiers, versions and requirement, control and evidence relationships. Do not copy another organization’s data.
  3. Validate before accepting data. Check the accepted and rejected record report; fix missing fields and invalid links before retrying.
  4. After import, compare record count, schema version and manifest with the prepared scope. Open selected records and check their sources. Importing source material or a draft does not activate requirements; review and approval are still needed.

Prepare an export and check receipt

  1. Define purpose, recipient, period and data scope. Confirm required permissions and approvals. An auditor’s package should contain only the agreed material.
  2. Prepare the file or package using the available operation. Check the manifest, document versions, checksums and export report. Retain its preparation date and sharing scope.
  3. The recipient checks completeness and readability. Moving data to another solution requires a separate format and relationship check; export alone does not demonstrate a successful migration.

If you need an external system connection

First describe the data, exchange frequency, recipients and business outcome. Check whether controlled import and export meet the need. Do not configure undocumented endpoints or shared accounts. Discussing a future integration does not make it part of the current offer.

Export guide · Training task guide · Discuss requirements