To find out what a person has with the company, someone opens module after module and builds the answer by hand.
The CPF profile searches every record at once and shows each link with the module, the role and a shortcut to the record.
Business management · Master Data (MDM)
The same person is a graduate, the financial guarantor of another graduate, a freelancer and a CRM customer, in records that do not talk to each other. Type the CPF and see where they appear in more than 30 records across the platform, the consolidated record with the source of each field, what they owe and how many tickets they have. Record quality points out invalid CPFs, records without a CPF and names that do not match, and the data subject report answers the LGPD request, with a record of who looked it up.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
To find out what a person has with the company, someone opens module after module and builds the answer by hand.
The CPF profile searches every record at once and shows each link with the module, the role and a shortcut to the record.
The graduate's name is spelled one way in the contract, another in the app and a third way in finance.
The consolidated record shows the values from each source, flags the mismatch and lets the steward pin the correct value with a reason, with a history of who decided.
Nobody knows how many records have no CPF or an invalid one.
Record quality shows, source by source, how many records have a CPF, how many do not and how many are invalid, with spreadsheet export.
The committee sent a spreadsheet with 300 CPFs and the question is who is already in the database.
The batch check takes up to 500 pasted CPFs and returns a CPF by module matrix, with invalid and not found flagged.
An LGPD data access request arrived and nobody knows where to start.
The data subject report gathers everything the company holds on that CPF, with the issue date, ready to export and print.
There is no way to say who looked at a person's data.
Every profile opened, report issued and list checked goes into the access log, with who and when, and the log can be filtered by CPF.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
A graduate's mother called to complain about a charge, and the support team did not know she also worked as a freelancer at the events.
Her CPF opened the profile with her links as financial guarantor, freelancer and app user, plus a summary of the open installments.
Support solved the charge knowing who they were talking to, without opening three modules.
A graduate appeared with an abbreviated surname in the pre-registration and the full one in the signed contract.
The profile showed the mismatch and picked the name from the contract, the most trusted source. The steward confirmed the value with a reason.
The consolidated record started showing the correct name, and the team fixed the source pre-registration through the profile shortcut.
A former graduate asked, under the LGPD, for a list of everything the company held on him.
The profile was opened by CPF and the data subject report was issued with the issue date.
The answer went out the same day, and the access log kept who issued the report.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
6 modules and 28 features on this page, all running on the same class, graduate and event records.
Where the CPF appears, in which role and what it has with the company.
The value that counts for each field, and where it came from.
When sources disagree, someone decides, and the decision is recorded.
Where the wrong, missing or conflicting CPFs are.
Paste the spreadsheet and find out who already exists in the company.
The data subject request answered, and every lookup recorded.
Compare the modules and choose the setup that fits your operation.