DATE:
AUTHOR:
Mo at Griffin
RELATED ROADMAP ITEMS:
☑️ Improved payment approvals
App Payments

We've added new payments roles to give you more control over approvals

DATE:
AUTHOR: Mo at Griffin
RELATED ROADMAP ITEMS: ☑️ Improved payment approvals

Previously, we had a single role for all Payments related actions in the app. After feedback on needing approvals, we’ve now split this role into three roles:

  • Request payments - you can submit a payment but it will not be processed until approved

  • Approve payments - you can approve payments submitted by other users but cannot approve your own payments

  • Approve own payments - you can submit payments and they will be instantly approved

For the admin user with your API key, make sure to select the Approve own payments role.

Payments waiting to be approved will now be shown in a Requests queue in the app. Each payment screen will also show a timeline showing when payments were submitted and approved.

How can I change user permissions?

  • Go to Settings

  • Select the user

  • Select Change roles

  • Update their permissions

How will this affect existing integrations?

Your existing integration won’t be affected. Any user or API key with the old Payments role will have that role replaced with the new Approve own payments role, so there will be no change in what they can do.

If you want to take use the new approvals flow, you can remove Approve own payments and assign the appropriate role, Request payments and/or Approve payments, to each user.


Thanks for reading!

Ready to explore? Sign up for our sandbox to start testing.

Need help? Send us a message at product@griffin.com.

 Read our docs

 Join our Slack community

Try our Postman collection

 Follow us on LinkedIn

Powered by LaunchNotes