Using Affinity on a single (mac OS) machine that has two user accounts -- one only, or both?

[KernalKorn]

Hello everyone,

I am brand new to Affinity & loving it already.

One question arises however, and I'm just not sure to which forum topic it is properly directed:

I'm a registered owner with Affinity installed on a single computer (mac OS 13.2.1), who uses 2 different OS User Accounts on that machine in order to keep task environments unique. 

I'm able to launch the Affinity apps within the OS User environment that I was logged into when I installed them without a problem, but I encounter an Affinity username / password challenge when I launch the apps if I'm logged into the other User environment.

I stopped short of resubmitting the information requested by that login challenge, because I don't want to mess anything up.

Instead, before I do that, I want to ask first whether I must restrict my enjoyment of Affinity apps only to the OS User Account I was using when they were first loaded (and where they are currently working fine) -- or if it is possible to use them in both OS User environments, once I enter the Affinity username / password info again in that second OS User Account.

The latter scenario would be super helpful to me, as there are occasions when I want to make edits on the fly when I'm logged into that second user environment -- but I can totally understand if "it just doesn't work that way."

(The challenge I'm seeing in the second User environment might be a matter of the way Permissions on my machine are set for Affinity, but I don't usually monkey around with permissions unless I know for sure that it's OK to make changes.)

If my description isn't sufficiently clear, I'm happy to rephrase this inquiry.

With apologies for such a basic question, and with great appreciation,

kk

Edited January 5, 2024 by KernalKorn

[v_kyr]

See related for macOS ...

• Are Installed Applications Useable by All User Accounts?

• How to Run GUI Apps as root in Mac OS X

• Run OS X apps as root

• How to Open Applications With Root Privileges on a Mac

• ... and so on, just do a websearch after that macOS related topic ...

[walt.farrell]

1 hour ago, v_kyr said:

See related for macOS ...

• Are Installed Applications Useable by All User Accounts?

• How to Run GUI Apps as root in Mac OS X

• Run OS X apps as root

• How to Open Applications With Root Privileges on a Mac

• ... and so on, just do a websearch after that macOS related topic ...

I'm not sure any of those are relevant to this question.

@KernalKorn: If all the user accounts are you, you're certainly allowed to use the app under any of your accounts. 

[v_kyr]

39 minutes ago, walt.farrell said:

I'm not sure any of those are relevant to this question.

Of course they are, just read the first and following ones and you will know. - Other than that, if an app is installed via root privileages and grants access to all users, every system user can access & use those apps. The user management of macOS gives each user their own area and regulates exactly who is allowed to access what.

---

In slightly more detail ...

As a Unix descendant, the Mac system can handle multiple user accounts very well. This is also part of the security concept because it allocates each user their own storage area and prevents other users from accessing it without authorization. For each file and folder, there are precise regulations as to who can use it. This means that several people can easily share a Mac without getting in each other's way.

You can manage the accounts in the system settings in the “Users & Groups” area. New accounts are created here and configured appropriately.

Private area

Each user receives their private folder, the home or home directory, from the system. There are folders for special data such as documents, pictures, music and films, but also for the contents of the desktop or downloads. Since only the owner has access here, there is a “Public” folder for exchanging data with other users. All Mac users can only open this, and they can also put something in the “Mailbox” folder it contains. It actually works like a mailbox: you can put something in, but then neither take it out nor see what's inside.

User types & groups

macOS recognizes different types of users. First there is the administrator. He has very extensive rights, especially with regard to the configuration of the system. He can also change protected settings, for example in Users & Groups, Security or Startup Disk. Simply look into someone else's home directory in the Finder and open someone else's files, but he isn't allowed to do so either. Only the “root” user can overcome this hurdle. A kind of super administrator who can do anything. It is present by default but not active. For safety reasons, it should remain that way until it is actually needed in an emergency. The first user created when installing macOS is always an administrator.

The standard user is used for normal work with the Mac. Since simple malware usually works with the rights of the currently active user, you should not always be logged in as an administrator. Create a normal user for everyday work. If you ever need access to protected settings and functions, macOS will ask you for an administrator's login details anyway. You don't even have to register again.

However, the managed user is subject to adjustable restrictions. If you activate parental controls for a user, you can limit access to apps and many functions, for example specifying contacts in Mail and Messages or websites in Safari. You can also set usage times. Managed User is suitable not only for children, but also for freely accessible Macs to prevent Internet abuse or configuration changes.

In addition to these normal user types, macOS also knows two more: If you activate the guest user, they can log in without a password. He gets a private folder and can work with apps. Optionally, he also gets access to shared folders from other users. If the guest logs out, their private directory is automatically deleted.

The other is the share user. He can only log in to active shares over the network and not directly on the Mac, and he doesn't get a local home directory. Finally, you can assign users to groups.

Set access rights

Creating groups is particularly practical when assigning access rights. If you enable access for a group, you don't have to enter each user individually. The access rights for files and folders can be found at the bottom of their information window - shortcut Command (cmd) + (i) - in the Finder. For sharing in the network, you specify the rights in the “Sharing” settings area.

[KernalKorn]

Thank you for the links, I will look at them more closely, though the common aspect seems to be that I need to use the command line. I can do that, but will that be required every time I want to launch Affinity apps in my secondary OS User environment? ...Or is issuing that command something done once, and then not again?

And I'm still not sure whether or not I need to re-enter the Affinity username / pw data when logged into the secondary OS User Account, or if I need to change something when logged into the OS UA that Affinity will launch with.

It appears to me that from Walt.Ferrell's comment, I am allowed to use Affinity apps in my two environments (which, if I can get there, will be enormously helpful).

But as I mentioned previously, I'm usually a bit hesitant to go under the hood. Way back when I was getting my feet wet with the command line, the person who was introducing me to it also introduced me to the phrase "With great power comes great responsibility" (which I took with great respect!)

Thank you again for helping me!

kk

[v_kyr]

19 minutes ago, KernalKorn said:

I will look at them more closely, though the common aspect seems to be that I need to use the command line. I can do that, but will that be required every time I want to launch Affinity apps in my secondary OS User environment? ...Or is issuing that command something done once, and then not again?

Depends only on how the app has been initially installed (account wise as a user or admin account) and which privileages different system users have (see above my addition about User types & groups). So if an Affinity app has been generally installed under /Applications, usually all system users can access it, but the Affinity registration might recognize two different system users here. Thus you would have probably to register it for both users with your Affinity site credentials (same name/e-mail & pwd). - The cmd line is only used to force some program/app etc. to be executed explicite with root privileages instead of some one (a common user).

[KernalKorn]

1 minute ago, v_kyr said:

Depends only on how the app has been initially installed (account wise as a user or admin account) and which privileages different system users have (see above my addition about User types & groups). So if an Affinity app has been generally installed under /Applications, usually all system users can access it, but the Affinity registration might recognize two different system users here. Thus you would have probably to register it for both users with your Affinity site credentials (same e-mail & pwd).

OK, thank you! That clarifies things for me quite a bit. Just so long as re-entering the username / pw info in the second environment doesn't preclude my using it in the first, or some other "problematic result" -- I should be fine, but I will continue reading those links first.

Greatly appreciated,

kk

[KernalKorn]

Thank you all once again for your kind assistance.

...And the winner is...

After submitting my Affinity authorization credentials to the challenge presented on app launch in the secondary OS user environment, the situation is resolved with no adverse effect upon my ability to use the apps when I'm logged into the primary OS user environment.

I'm very psyched to be able to use the apps from within either OS user account, since that aids my work flow enormously. And I'm happy that -- in this case, at least -- the simplest solution prevailed since (as noted) I was reluctant to go digging around under the hood via the terminal screen.

Best regards,

kk