Requirements and integrations
What you need before implementing Clema
Clema connects to the systems your institution already runs on. Here are the prerequisites, the supported integrations, and what your IT and security team will need.
The short version
You need two things to start: a data source Clema can connect to, and a named admin to approve read-only access and sign the BAA. Clema connects to 50+ platforms across SIS, LMS, warehouses, and BI tools. Most institutions are live in 2 to 4 weeks.
Technical prerequisites
Not much. Three things and you are asking questions.
A data source
A warehouse, an SIS, an LMS, or a spreadsheet. In the trial, a sample source is enough to start asking questions.
A named administrator
Someone to approve read-only access to your sources, manage roles, and sign the BAA. Usually an IR director, IT director, or data governance lead.
Read-only access posture
Clema reads from your sources and never writes back without explicit permission. Source credentials stay governed by your admin and your security review.
Supported integrations
Clema connects to the systems your institution already runs on, plus file uploads and custom APIs.
Student Information Systems (SIS)
- Banner
- Colleague
- PeopleSoft
- Workday Student
- Jenzabar
- Custom SIS via API
Learning Management Systems (LMS)
- Canvas
- Blackboard
- D2L Brightspace
- Moodle
- Sakai
Data Warehouses & Databases
- Snowflake
- Amazon Redshift
- Google BigQuery
- Microsoft SQL Server
- PostgreSQL
- Oracle
BI & Analytics
- Tableau
- Power BI
- Google Looker
- Excel
- Google Sheets
Identity & Access
- SAML 2.0 SSO
- OAuth 2.0
- OpenID Connect
- Multi-factor authentication
File Uploads & Custom
- CSV and Excel uploads
- Google Sheets
- Custom APIs
- Webhooks
Typical implementation timeline
Most institutions are live in 2 to 4 weeks. The trial starts on day one.
Week 1
Connect sources
We help your admin connect the first data sources and confirm read-only access.
Week 2
Configure SSO and roles
SAML or OAuth SSO is set up, role-based access is configured, and the BAA is signed.
Week 3
Pilot with your team
Your IR team starts asking real questions on real data. We help tune definitions and connectors.
Week 4
Roll out
Stakeholders are invited, widgets are embedded where useful, and you are live.
Security review ready
For your CISO and IT security team, we provide the compliance pack under NDA, usually within one business day.
Integrations and prerequisites FAQs
What do I need before implementing Clema?
Two things: a data source Clema can connect to (a warehouse, an SIS, or a spreadsheet to start), and a named administrator who can approve read-only access and sign the BAA. Most institutions are live in two to four weeks.
Which student information systems does Clema integrate with?
Clema connects to Banner, Colleague, PeopleSoft, Workday, and most modern SIS platforms. We also support spreadsheet uploads and custom APIs for systems without a standard connector.
Does Clema integrate with our data warehouse and BI tools?
Yes. Clema connects to Snowflake, Redshift, BigQuery, and SQL Server, and complements Power BI and Tableau with a conversational layer. Your dashboards stay; Clema handles the ad-hoc questions.
What does Clema need from our IT and security team?
Read-only access to the sources you want Clema to query, a named admin to manage roles and access, and a signed BAA. We provide the SOC 2 Type II report and security documentation under NDA.
How long does implementation take?
Most institutions are live in two to four weeks, including data connections, SSO setup, and user training. The 14-day free trial connects a sample source so you see value in the first session.
Ready to connect your data?
Start a free 14-day trial, or book a demo and we will scope your integrations and timeline.