Introduction
OAuth lets users grant limited, revocable access to their RecordsKeeper.AI data. With OAuth Apps, you define the app’s branding, legal links, contact info, permissions (Purpose), and allowed redirect URLs. From there, you can review status, search apps, and revoke access anytime.
Where to manage OAuth Apps
Go to Widgets & Integration → OAuth Apps.
Use the list to see each app’s Name, Purpose, Created On, Last Updated On, Status (Active/Revoked), and Action menu.
Click Create OAuth App to add a new one.
Create an OAuth App (Step 1: OAuth Setup)
A setup modal opens. Provide the basics your users will see during authorization.
OAuth App Name - A clear name your users recognize.
Brand Name - Shown on the consent screen to build trust.
Policy & Term URL - Link to your privacy/terms page.
Brand Logo - Recommended 512×512 (1:1) JPG/PNG, max 500 KB so it looks sharp everywhere.
Brand Background Color - Accent color for the consent screen.
Summary - A short, plain-English line about what the app does.
Brand Contact - Name and Email for support or security notices.
Note - Internal context for your team (optional).
Click Next Step.
Define what the app can do (Step 2: Purpose)
Keep access tight and intentional.
Purpose Key - Choose what this app is for (e.g., a specific tool or capability category). This determines what data/actions the app can request.
Purpose Description - Clarify the use case so approvers and teammates understand why access is needed.
Redirect URL(s) - Add one or more exact callback URLs your app will use after the user authorizes. (Use separate URLs for dev/stage/prod.)
Select Create OAuth Client to finish.
Tip: If you later change domains or environments, update the Redirect URL(s) here - OAuth will only redirect to whitelisted URLs.
Connect your external tool
In your external tool, choose RecordsKeeper.AI (or your app name) as the connection method.
The user is taken to a branded consent screen with your App Name, Logo, and Purpose.
After granting access, the user is returned to your registered Redirect URL where your app can complete the connection.
(Exact steps vary by the tool; follow that product’s “Connect via OAuth” flow using the app you just created.)
Manage existing OAuth Apps
From OAuth Apps:
Search & sort to find apps quickly.
Check Status at a glance (Active/Revoked).
Use the Action menu to view details or take app-level actions.
Revoke an app to immediately block new authorizations and access; restore by creating a new app or re-authorizing as needed.
Practical tips
Create separate apps per environment (Dev, Staging, Prod) with distinct redirect URLs.
Keep the logo small and square (512×512) for best rendering.
Make your Summary user-friendly; it appears on consent and reduces confusion.
Review apps quarterly - revoke anything unused or owned by departed vendors.
If users report “redirect mismatch,” verify the exact Redirect URL(s).
Conclusion
OAuth Apps give you a clean, branded, and secure way to connect RecordsKeeper.AI with other services. Set up the app once with clear branding and strict redirect URLs, define a precise Purpose, and manage access centrally - so integrations stay seamless and safe.