Creately Atlas Product Schedule
Product-specific terms for the organizational planning platform
| Provider | Cinergix Pty Ltd (ABN 69 130 459 906), trading as Creately |
| Version | 1st July 2026 |
| Registered office | Unit 1, 20 Collins Street, Mentone, Victoria 3194, Australia |
Applies with an Order Form This Product Schedule supplements the Creately MSA for an Order Form subscribing to Creately Atlas. Capitalised terms not defined here have the meanings in the MSA.
1. Atlas service
1.1 Atlas is an organizational-planning platform that connects People, Positions, reporting relationships, position occupancy, succession information and related workforce data into an organizational model and presents that model through charts, rosters, search, directory, succession, scenario and workforce-insight views made available in the subscribed edition.
1.2 The specific modules, usage limits, connectors, environments and support plan purchased by the Customer are stated in the Order Form.
1.3 The Customer’s HRIS or other designated source remains the system of record for underlying employment data unless the parties expressly agree otherwise in writing.
2. Authorised use and user categories
| Category | Typical rights | Commercial treatment |
|---|---|---|
| Administrator | Configure workspace, mappings, access and integrations. | Named user unless Order Form states otherwise. |
| Planner | Create and review scenarios, succession plans and workforce views. | Named user unless Order Form states otherwise. |
| Manager / restricted viewer | View data within granted organisational or field scope. | As stated in Order Form. |
| Directory viewer | Use approved directory/search experience. | As stated in Order Form. |
| Integration account | System-to-system access for configured connector. | Not a human user; subject to connector limits. |
2.1 Credentials are individual unless a documented integration requires a service account. The Customer must not share human-user credentials.
2.2 The Customer may expose an approved embedded directory or search experience to its workforce and, where expressly stated in the Order Form, to authorised users of its own customer-facing environment. This does not permit general resale of Atlas.
3. Customer Data and data model
3.1 Customer Data may include names, contact details, job and position information, reporting relationships, location, organisational attributes, succession candidates, talent assessments, compensation information, demographic information and other fields configured by the Customer.
3.2 The Customer controls which fields are imported, displayed, made searchable or made available in planning views. The Customer is responsible for classifying sensitive fields and configuring access appropriate to its policies and applicable law.
3.3 Atlas may generate derived organisational relationships, projected structures, calculations, insights and scenario data from Customer Data. These are Customer Data under the MSA.
4. Access controls
4.1 Atlas supports role-based and field-level access configurations. Access may be scoped by explicit grants, organisational position, reporting relationship, user role, view, environment or other configured criteria.
4.2 The Customer is responsible for validating access rules before production use and after changes to source data, roles, reporting lines, integrations or permissions.
4.3 Creately will apply configured access rules, but cannot determine whether a particular person should be entitled to view a field or record. The Customer remains responsible for entitlement decisions.
5. Integrations and write-back
5.1 A connector may read data from an HRIS, identity platform, file source or other Customer-designated system. Connector scope, frequency, direction and supported objects depend on the configured integration and Order Form.
5.2 Any write-back from Atlas to a source system is disabled unless specifically configured and authorised. The Customer is responsible for reviewing, approving and reconciling write-back operations and for maintaining appropriate source-system backups and controls.
5.3 Creately is not responsible for changes, outages, rate limits or discontinued functionality in a third-party API, but will use reasonable efforts to maintain supported connectors and communicate material impact.
6. Implementation and data quality
6.1 Implementation services, deliverables and acceptance are governed by the SOW. Unless the SOW states otherwise, the Customer is responsible for source-data extraction, cleansing, validation and business sign-off.
6.2 Atlas outputs depend on Customer Data, mappings, configuration and assumptions. The Customer must validate data and outputs before use in material workforce or employment decisions.
6.3 Creately does not provide employment, legal, tax or regulatory advice through Atlas.
7. AI and automated features
7.1 If an Atlas feature uses machine learning or generative AI, Creately will identify the feature in the Service or Documentation. The Customer controls whether to enable optional AI features where that control is offered.
7.2 AI-generated or probabilistic outputs may be incomplete or inaccurate and require human review. Atlas is not intended to make final decisions about hiring, promotion, termination, compensation, succession or other employment matters without Customer review.
7.3 Customer Data will not be used to train a general-purpose or shared model except with the Customer’s express written authorisation, consistent with the MSA and DPA.
8. Usage limits and changes
8.1 The Customer must remain within the managed-population, named-user, connector, environment, storage and other limits in the Order Form. The parties will discuss a good-faith upgrade if usage materially exceeds a limit.
8.2 Creately may update views, workflows and interface design, provided it does not materially reduce the core subscribed Atlas functionality as a whole during the current Subscription Term.
8.3 New modules, premium connectors or materially expanded functionality may require an additional Order Form.
9. Export and transition
9.1 Available exports may include CSV, spreadsheet, image, PDF or other documented formats depending on the view and edition.
9.2 If the Customer requires a custom transition export or migration assistance beyond standard export features, Creately may provide it under a mutually agreed SOW.
10. Beta and preview functionality
10.1 Beta, preview or evaluation functionality is optional, may change or be discontinued, and is excluded from service levels unless the Order Form expressly states otherwise. Creately will not knowingly use beta functionality to process production sensitive data without Customer approval.