Today’s update brings a large change to how permissions are assigned in CloudBridal. Prior to this change, CloudBridal worked by giving the store owner full access to all sensitive data and settings, with all staff added to the store being given a default limited set of permissions. All added staff would be able to access and manage all orders, customers, inventory items, and appointments. However, since many staff members have differing responsibilities, we decided to undertake an initiative to give you total flexibility over assigning what your staff can see and do within CloudBridal.


Put simply, a role represents a set of things a user can do. For instance, the Admin role that comes standard by default is a role that can do everything. You can now create your own custom roles and assign permissions to them. For example, you can create a Sales Associate role that has the ability to manage your customers and orders. You can create as many roles as you want, but a single user can only have one role.




A permission defines the ability for a user to perform a specific action. For example, the ability to view customers or to manage appointments. You can configure permissions for new roles that you create.



Putting Roles and Permissions Together

Once you create a role and add some permissions to it, you can then assign this role to a user. The next time the user logs into CloudBridal, they will only be able to do what their role lets them do. For example, if you only set the View Appointments permission, that user will only be able to view appointments in CloudBridal. They will not have the ability to create or manage appointments, and they will also be restricted from accessing any other parts of the site. In addition to restricting access, these changes have the added benefit of actually making it easier for your staff to efficiently use CloudBridal. By defining roles for your staff, you can help simplify the interface to reduce confusion and increase their productivity.


Future Feature Implications

Fundamentally, these changes will help us create path toward the types of features we wish to focus our development resources on. Until now, we never had a good approach for developing role-specific features, such as a word orders feature for seamstresses. Creating such a feature would needlessly bloat the interface, making it increasingly more difficult for other users like sales associates to use CloudBridal. Now with the concept of roles, we are able to create specific features like this and then encourage you to create roles that are dedicated to these features. We are definitely excited to see what the future brings in terms of next-gen bridal shop management.


In Other News

There are also a number of minor fixes and enhancements with this update:

  • Fixed bug where card headers had issues when adjusting screen width
  • Disabled Google Chrome form autocomplete for several fields where it is irrelevant
  • The “Order Is Late After This Many Days” setting now calculates from an order’s expected arrival date instead of its ordered date. Additionally, the alert text has been changed to specify how many days late the order is
  • Other minor wording changes and bug fixes