OpenText Corporation

OpenText Core for UK G-Cloud

OpenText Core is a SaaS service which runs in the OpenText Cloud. Securely share, sync and collaborate on enterprise content from any device even when offline, receive contextual notifications and track activity via audit and version history. Administrators have complete control over enablement of users, security polices, authentication and integrations.


  • Simple Secure collaboration with third parties eg partners or suppliers
  • Share, Sync and work on any device
  • Security for files in transit, at rest, in the cloud
  • Deep integration with Microsoft
  • Simple ad-hoc Workflow
  • Advanced Search options
  • Exportable Audit trail, to track what is shared internally/externally
  • Shared content can be pulled back at any time
  • Reporting dashboards allow administrators to manage system activity
  • Highly secure data centres in the UK and EEA


  • Full permission control of content
  • Deploys instantly with high scalability in the cloud
  • UK and EEA hosting services
  • Predictable operating cost, lower TCO
  • Improves user productivity
  • Streamline business processes with workflow
  • Extends reach of existing ECM environment including ContentSuite and Documentum
  • Highly secure
  • Administrators can remotely wipe local content on mobile devices
  • Eliminate rogue file sharing applications


£102 per person per year

Service documents


G-Cloud 11

Service ID

6 1 5 0 1 0 8 5 1 6 4 7 8 8 6


OpenText Corporation

Gideon Jones


Service scope

Service scope
Software add-on or extension No
Cloud deployment model Public cloud
Service constraints Prior to agreeing contract, buyers should contact OpenText to confirm terms, solution and scope.
System requirements Not applicable. The service is provided using OpenText Cloud infrastructure.

User support

User support
Email or online ticketing support Email or online ticketing
Support response times Support levels for Priority 1 (Critical) calls will remain the same (24x7).
For all other priority calls - standard hours are 8am - 5pm Monday - Friday.

The Response Time commitments vary by the classification of the request, as per the list below:

• 1 hour Service request classified as Critical
• 2 hours Service request classified as Serious
• 4 hours Service request classified as Normal.

Additionally for the OpenText Core solution - any customers that have an active OpenText Customer Support contract can leverage that support contract to open a OpenText Core support request.
User can manage status and priority of support tickets No
Phone support No
Web chat support No
Onsite support No
Support levels Support issues are raised either via email or on the Core Support Forum.
Support available to third parties No

Onboarding and offboarding

Onboarding and offboarding
Getting started The solution is designed to be intuitive. Online context sensitive help is provided. Any additional requirement for Training would need to be agreed with OpenText at an extra cost prior to contract.
Service documentation Yes
Documentation formats PDF
End-of-contract data extraction The OpenText Core Terms and Conditions outlines the description of services provided, including any data return or data destruction obligations.

Any User Content stored on your Account that has been backed-up by us will be held for 90 days before being automatically deleted. We strongly recommend that you download and save your User Content onto an alternative storage medium before cancelling your Account and Subscription. If you would like to recover any User Content that may be held within these 90 days, please contact us at:
End-of-contract process At the end of the contract, customers are given a 90 day period during which they are able to extract their own data.

Further details are provided in our terms and conditions documentation.

Using the service

Using the service
Web browser interface Yes
Supported browsers
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
Application to install No
Designed for use on mobile devices Yes
Differences between the mobile and desktop service Interfaces are optimised for the client device accordingly.
Service interface Yes
Description of service interface Browser interface.
Accessibility standards None or don’t know
Description of accessibility Via browser interface.
Accessibility testing None.
What users can and can't do using the API The API is not designed for End Users. Any interaction with the API would need to be agreed and designed and/or approved by OpenText Professional Services.
Additionally should a Sandbox / Test environment be required for our API, this can be arranged at an additional cost.
API documentation Yes
API documentation formats
  • HTML
  • PDF
API sandbox or test environment Yes
Customisation available No


Independence of resources OpenText Core is a SaaS application designed to support multi tenancy and is dynamically scaled automatically according to demands being placed upon it.


Service usage metrics Yes
Metrics types Both Users and Administrators are provided with a dashboard view which delivers data on service usage.

Adminstrators can see the overall storage utilisation for their environment as well as breakdowns of file types, usage per user as well as view who has been invited to collaborate securely within Core.
Reporting types Real-time dashboards


Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Other security clearance
Government security clearance None

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations No
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency Less than once a year
Penetration testing approach In-house
Protecting data at rest
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Other
Other data at rest protection approach All data at rest is encrypted with AES256. Files are stored in distributed data centers with unique encryption keys for each client. Our encryption solution leverages Hardware Security Modules (HSMs) with tamper-proof backups that allow for physically secure file storage and data loss prevention.
Data sanitisation process Yes
Data sanitisation type Explicit overwriting of storage before reallocation
Equipment disposal approach Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data importing and exporting
Data export approach Customers can utilise the app download features to download data.
Data export formats Other
Other data export formats Dependent on source format.
Data import formats Other
Other data import formats
  • This is dependent on source format.
  • Almost any digital format is supported.

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks TLS (version 1.2 or above)
Data protection within supplier network TLS (version 1.2 or above)

Availability and resilience

Availability and resilience
Guaranteed availability OpenText Core availability is typically above 99.5%.
Approach to resilience All OpenText datacenters are TIA942 Tier 3+ compliant. We also provide disaster recovery datacenters within the EEA.
Outage reporting Email alerts are used - authorized points of contact (“POCs”) will be notified as soon as possible or within 24 hours.

For Planned Outages customers are notified in advance via a post on the Core site and via a direct email to POCs.

Identity and authentication

Identity and authentication
User authentication needed Yes
User authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
Access restrictions in management interfaces and support channels Our Cloud Services User Access Management policy restricts user access based on least privileged access guidelines. Workforce members are only granted rights to access assets needed to fulfil the job functions. Validation is enforced through a full life cycle for identity access management process, and a bi-monthly validation of all access privileges per policy.
Access restriction testing frequency At least every 6 months
Management access authentication
  • 2-factor authentication
  • Dedicated link (for example VPN)

Audit information for users

Audit information for users
Access to user activity audit information Users have access to real-time audit information
How long user audit data is stored for At least 12 months
Access to supplier activity audit information Users have access to real-time audit information
How long supplier audit data is stored for At least 12 months
How long system logs are stored for At least 12 months

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification Yes
Who accredited the ISO/IEC 27001 Schellman
ISO/IEC 27001 accreditation date 09/07/2018
What the ISO/IEC 27001 doesn’t cover None. This certification process is renewed each year.
ISO 28000:2007 certification No
CSA STAR certification No
PCI certification No
Other security certifications No

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance certified Yes
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards SSAE-18 SOC1 Type II
SSAE-18 SOC2 Type II
Information security policies and processes OpenText has a Global Information Security Policy based on ISO 27001:2013. The details of this policy are confidential. If required, OpenText will be prepared to discuss this policy and details of how these policies are followed on a one to one basis with our customers subject to an agreed NDA.

Operational security

Operational security
Configuration and change management standard Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach OpenText follows a fully mature ITIL Change Management process. More details are available upon request.
Vulnerability management type Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach Monthly industry standard vulnerability scanning. Annual external vulnerability scans. Results are collected, prioritized, and assigned to owners using the Common Vulnerability Scoring System.

Unified Threat Management system has updated real-time Anti-Virus and Intrusion Prevention services. Security intelligence feeds from industry leading & government organizations such as CCIRC in Canada or US-CERT in the United States.

All critical vulnerabilities via a vendor patch, remediation asap but not later than 30 days of identification and release of appropriate system/application patch.

All required system upgrades or patches, remediation within 90 days of their identification and the release of an appropriate system/application patch.
Protective monitoring type Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach This is covered by the OpenText Information Security Incident Management policy described within section 16 of the GISP. Due to sensitivity of security issues, the GISP and ancillary documents are considered OpenText Confidential. This can be discussed one to one with a prospective customer under a mutually signed NDA.
Incident management type Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach This is covered by the OpenText Information Security Incident Management policy described within section 16 of the GISP. Due to sensitivity of security issues, the GISP and ancillary documents are considered OpenText Confidential. This can be discussed one to one with a prospective customer under a mutually signed NDA.

Secure development

Secure development
Approach to secure software development best practice Conforms to a recognised standard, but self-assessed

Public sector networks

Public sector networks
Connection to public sector networks No


Price £102 per person per year
Discount for educational organisations No
Free trial available Yes
Description of free trial Open Text Core has a free Personal User Licence option - for securely storing and sharing your files and collaborating with friends and family. It offers the following:
1 User licence
2 GB Total Storage
250 MB Max File Size
Mobile Access
Desktop Sync
Advanced File Versions
Two-Factor Authentication
Link to free trial

Service documents

Return to top ↑