Use case summary
Invite your team into one Corefy organization and give each member a role that opens only the dashboard sections their job needs. Viewer reads, Manager edits business settings, Administrator manages the team, and custom roles cover everything in between. Every change carries a named user, so no one shares a login to get work done.
- Payment Manager
- Payment Ops
Why payment work ends up scattered across logins
Every provider your company works with arrives with its own portal and its own set of logins. As the stack grows, so does the number of places where payment work happens.
Ops chase a failed transaction in one portal while finance exports settlement files from another. 49% of companies now use 5 or more systems to manage payments, and 13% run across 10 or more.
The workarounds are predictable: shared credentials because seats cost money, a spreadsheet tracking who has access to what, and a support request that waits until the one person with the right login is online. Access becomes both a bottleneck and an audit gap.
How to put the whole team in one workspace
Corefy organizes access around a single organization account. You invite people and decide what each person can open.
- 1
Invite the team into one organization
Go to Administration settings, open Profile, then Members, and click Invite New members. Enter an email, pick a role, and send. You can invite up to five people at a time; the invite expires in 72 hours, and you can revoke or resend it while it is pending.
- 2
Assign a role that matches the job
Four default roles cover the common cases. Viewer reads the data in the account without updating any field. Manager manages company data and updates business settings. Administrator has full access, except for modifying the Owner. Owner has full access with no restrictions.
- 3
Create a custom role where the defaults don't fit
Open the Roles tab, click Add a new role, and give it a name and description. You can copy the permission set of an existing role as a starting point, then set each entity to None, Read only, or Write. Custom roles appear in the invite dropdown next to the default ones.
- 4
Keep the changes traceable
The audit log records system events in the organization with the user behind each one, so a role change or a configuration edit has a name and a timestamp attached to it.
- 5
Update access as the team changes
Open a person's Member Info page to change their role. Click Disable, and their access to the organization ends, while their account stays a system account they can use elsewhere. Managing members belongs to the Owner and the Administrator.
What you get
Access stops being a support ticket and becomes a setting.
One login per person
Each team member holds a single account covering every connected provider.
Permissions that match the job
People open the sections their work requires and nothing beyond them.
A record of who changed what
Role edits and configuration changes carry a named user and a timestamp.
Onboarding and offboarding in minutes
A new hire gets working access on day one, and a leaver loses it in one action.
One interface, 79% approval rate across the stack
Grand Cru Concepts publishes digital entertainment platforms across the US and Canada. Before Corefy, the team moved between separate provider dashboards with isolated routing logic and custom code for every integration. A year after go-live, the entire stack runs from one interface. Karla Gomez, Head of Payments, reports that her team monitors activity, reviews transactions, and coordinates with providers without switching systems. As of May 2026, the stack holds a 79% approval rate with no declines attributable to platform instability, covering cards, ACH, Google Pay, Interac e-Transfer, and crypto.