Hi Bubble community, I am trying to create a SaaS app where essentially a user can create a property/entity to then charge payments through.
The four common solutions I’ve found are(I’ve read through the other forum posts):
- Use a sequential number
- Use a random number
- Use a combination of letters and numbers
- Use a unique identifier
Each has it’s own host of issues for example sequential may have doubled up users if they register at the exact same time. Random numbers may not be the best either if there is not defining structure to how it is generated.
Since the property entity will be used in the url for navigation, my main concern is security so that you can’t just put in the SN of the property and you access an account that isn’t yours. Is this even a concern or just handled in the privacy settings?
I see companies like Salesforce has their account SN numbers which I assume is for security reasons so I am leaning towards a scrambled SN but I could be approaching this wrong.
Any tips on how to best implement this while focused on security, ease of implementation, and scalability would be great.