Review Grella’s current approach to signed-in access, organization and matter permissions, work-product action records, and security hardening.
Data handling
Review the current data scope.
Know which matter content is in scope, how AI features process it, and what your firm still needs to confirm.
Content in scope
Identify the matter files, facts, answers, and work included in the review.
Provider use
Grella uses business APIs to provide its AI features.
Your requirements
Confirm storage, retention, model use, and contractual needs with Grella.
Access controls
Limit work to the right people.
People only see the matters they are allowed to work in.
Signed-in user
A user has to be signed in before any matter work is available.
Right firm
The account has to belong to the right firm.
Assigned matters
The user can only open matters they have permission to see.
Allowed work
Their role sets what they can do inside that matter.
Audit logging
See who did what, and when.
Grella keeps a record when work product is created, changed, exported, removed, opened, or restored.
Created
A new work product is added to the matter.
Edited
An existing work product is changed.
Exported
A work product is taken out of Grella.
Deleted
A work product is removed.
Opened
A work product is opened.
Restored
A removed work product is brought back.
Questions firms ask before they start.
These answers stay within Grella’s current public claims. Broader requirements belong in a security review.
Discuss your requirementsAsk ChatGPT about Grella.
No. Access is limited by firm, matter, and role. A signed-in account is not enough to open every matter.
Security review
Share your security checklist.
Tell us what your firm needs to confirm. We will walk through the current controls, access model, and documents.