I recall reading there is a restriction on how many user profiles can be active at one time: 3. So if you want notifications to be sent in from other profiles, that's something to keep in mind.
Rate my Profile Isolation/Silos
jroddev Every app is individually sandboxed. Apps can't ever access each other's data and require user consent to access profile data. Profiles don't provide any additional sandboxing. Profiles provide separate workspaces with separate instances of apps, app data and profile data. Apps can't communicate or share data across user profiles other than via the network (mostly true for work profiles too) and apps can't see apps in other user profiles (but can see them to an extent across user/work profile boundary).
[deleted]
GrapheneOS Does that also mean if google play services are enabled then the apps in that user profile cannot "talk" to each other?
[deleted] Every app is sandboxed whether or not you use Google Play services. Apps can communicate with mutual consent within a profile and can't do that across profiles without using the network. Sandboxed Google Play compatibility layer enables using Google Play as regular apps in the full standard app sandbox. There's no special app sandbox for Google Play. It's the same full app sandbox as every other app you install. GrapheneOS provides our sandboxed Google Play compatibility layer to make it work that way, not a special sandbox for it.
@"GrapheneOS"
Could you provide more information around 'mutual consent' to help with my understanding? I saw this used in the docs and I'm not sure what it means in practice. Does this mutual consent involve user approval? Or do the apps themselves provide the consent? What are the mechanism/s?
It has been a few years since I've done any Android dev but at the time we were communicating with intents and app-links. I'm also aware you can communicate using storage shared folders, or via the network.
jroddev what the doc calls "mutual consent" and "interprocess communication"/IPC is intents. Intents require mutual consent as the dev of the calling app obviously agreed to interact with the app they are calling and the dev of the receiving app wrote in their manifest which app can trigger which intent. At least, that's my understanding.
- Edited
Based on the response from @GrapheneOS I have semantically corrected the thread title and rephrased the OP to change references to 'sandbox' to user profiles or users.
Hi, how has your work set-up been running?
I am using a very similar applications and profiles set-up to yours.
I have not been able to get the Pagerduty app to run. Pagerduty reports a "Security Threat REF: 143:248C". I suspect they think my GrapheneOS is a rooted Android phone.
Is yours running OK? If so, do you have any suggestions for configuring the profile?
Many Thanks
- Edited
jroddev Any other recommendations or thoughts?
jroddev I may be forced to merge the Owner, Personal, and Personal Secure profiles to some degree. I was hoping to keep the actual Password Vault + App separate and only move individual credentials when I need them. Merging it all together is no different than I have now though.
You may benefit from considering separating profiles based on the restrictions GrapheneOS provides, this is regarding the phone/SMS and app installation permissions that you can grant to profiles individually.
For example, your personal and Google Anonymous Profiles don't seems to need SMS/Phone permission. It will prevent accidentally giving the phone permission to any app there (https://discuss.grapheneos.org/d/14967-information-on-phone-permission).
Just wondering how you are going to install the apps in profiles without 3rd party app managers.
You can install apks but you have to manage the updates yourself which will be a very time consuming practice.
panopticon Im curious to hear what others use to share files between profiles
I use signal for sharing between profiles