Jay - to provide more context - Quick Base loads your application when you open it. When you have cross-app relationships - Quick Base also then goes and loads those applications from memory too. So basically if you have 5 connected apps - and you open one - Quick Base sees that and loads all 5 for you regardless of which you opened so it operates in practice kind of like one big app as far as the work Quick base has to perform. So in regards to size and complexity - they're comparable. Based on 50 - 100 users - unless you're loading millions of records across your system - this probably won't be an issue.
As for security - it's not really any different whether its in one app or several. You still have full control over what permissions users should or shouldn't have to certain fields/tables etc. As I mentioned before - my experience has been that when everyone is in a single app you end up creating one off roles and overly complicated permission sets to account for specific use cases where different people in similar roles in your company need to do specific / unique things in your system. Think about if you have resource data somewhere. If you break it into its own app - you can only allow certain people to view and manage it in that one app. But if its in the same app - you might have some users who all perform the same daily function - but also have some HR responsibilities and they're the only person on that team who can see the resource data. Things like that necessitate a broader role set in a single application. Certainly not a technical issue - just an annoyance to have to manage a lot of roles.
You're correct though - navigation can be a little odd if people don't always know where information is stored in some cases if everything isn't in the same app
Chayce Duncan | Technical Lead
(720) 739-1406 |
chayceduncan@quandarycg.com Quandary Knowledge Base
