Setup guide
How to set up Clema end to end
A complete implementation walkthrough: connect sources, configure SSO and roles, sign the BAA, pilot with the IR team, and roll out to stakeholders. Most institutions live in 2 to 4 weeks.
The short version
Four phases, two to four weeks: connect sources, configure SSO and roles, pilot with the IR team, roll out. Clema provides an implementation lead; you provide a named admin with authority to approve read-only access and sign the BAA.
The four phases
Week 1
Connect your data sources
Provision read-only credentials for the sources Clema will query. We help connect your SIS (Banner, Colleague, PeopleSoft, Workday), warehouse (Snowflake, Redshift, BigQuery), LMS (Canvas, Blackboard), and file uploads. The free plan can run on a sample source while production connectors come online.
Who's involved: Your named admin (IR director, IT director, or data governance lead) provisions access; Clema's implementation lead runs the connector setup.
Closes with: Closes when read-only access to at least one production source is confirmed and test queries return correct results.
Week 2
Configure SSO and roles
Set up SAML 2.0 or OAuth 2.0 SSO with your identity provider. Configure role-based access so the right people see the right data. Sign the BAA governing FERPA-ready data processing. Confirm encryption (AES-256 at rest, TLS 1.3 in transit) and the audit trail posture with your security team.
Who's involved: Your IT/identity team configures SSO with Clema's implementation lead; your named admin and legal counsel sign the BAA.
Closes with: Closes when SSO login works end to end, roles are assigned, and the signed BAA is on file.
Weeks 2-3
Pilot with the IR team
Run real questions on real data for one to two weeks. Tune IPEDS definitions, connectors, and terminology so Clema speaks your institution's language. Confirm the audit trail and source attribution on shipped answers. Decide which questions go to Clema and which stay with dashboards.
Who's involved: The IR/IE team runs the pilot day to day; Clema's implementation lead tunes definitions and connectors based on their feedback.
Closes with: Closes when the IR team signs off that sourced answers match what they would produce by hand, and the question-routing split (Clema vs. dashboards) is decided.
Week 3-4
Roll out to stakeholders
Invite deans, chairs, and the cabinet to ask questions in plain English. Embed Clema widgets in Power BI, Tableau, or your IR portal where useful. Set up the data-request queue if you are running intake through Clema. Confirm the support path with the IR admin.
Who's involved: The IR director drives the invite list and widget placement; deans, chairs, and cabinet members are the new users being onboarded.
Closes with: Closes when stakeholders are invited, any widgets are live, and the IR admin has confirmed the ongoing support path.
Tools you can connect
Clema connects to the systems your institution already runs on, plus uploads and custom APIs.
Setup FAQs
How long does it take to set up Clema?
Most institutions are live in 2 to 4 weeks. Week 1 connects data sources, week 2 configures SSO and roles and signs the BAA, week 3 runs a pilot with the IR team, and week 4 rolls out to stakeholders.
What does Clema implementation include?
Connecting your data sources (SIS, LMS, warehouse, files), configuring SSO and role-based access, signing the BAA, pilot onboarding with your IR team, tuning definitions and connectors, and rolling out to stakeholders with widgets where useful.
Do we need a dedicated project manager for setup?
No. Clema provides an implementation lead who coordinates connections, SSO, and onboarding. You need a named admin on your side with authority to approve read-only access and sign the BAA.
Can we pilot Clema with one team before rolling out?
Yes. Most institutions pilot with the IR team for one to two weeks, tune definitions and connectors on real questions, then roll out to deans, chairs, and the cabinet.
How does Clema connect to our data warehouse?
Clema connects to Snowflake, Redshift, BigQuery, SQL Server, PostgreSQL, and Oracle with read-only credentials your admin provisions. We never write back without explicit permission, and every query carries an audit trail.
Ready to set up Clema?
Book a demo and we will scope your setup timeline, or start free on a sample source today.