Consent
Consent in Indacas is built for evidence: people never agree to a document that can quietly change underneath them. A consent statement goes through a draft → publish lifecycle, and every acceptance is recorded against the exact published version the person saw.
Kinds of statement
A study can hold three kinds of statement: consent (the classic research consent form), NDA, and agreement (anything else people must accept). All three work the same way.
Writing and publishing
Create a statement from your study’s Consents page. You write the body in plain language (it supports formatting), set the label on the agreement checkbox — by default “I have read and agree to the above” — and choose whether acceptance also requires a typed signature.
While a statement is a draft, you can edit it freely, but it can’t be used anywhere. Publishing freezes that version. A published statement can be added to onboarding flows as a consent step; only published statements are offered there.
Need to change a published statement? Just edit it — saving creates a new draft version, which you review and publish when ready. Earlier versions stay frozen, and everyone’s acceptance still points at the version they actually agreed to.
What gets recorded
For every acceptance, Indacas stores who accepted, when, which version of the statement they accepted, and their typed signature if one was required. The statement’s page lists all acceptances, so you can show an ethics committee exactly who agreed to exactly what wording.
Re-consent
If your protocol changes materially, publish the updated statement as a new version. Existing participants’ acceptances remain valid records of what they agreed to at the time; new joiners see the latest published version automatically.