Repository navigation
Apify CLI to support organizations the same way Apify Console does #445
Description
Apify CLI should support the organizations in an equal way to Apify Console UI, i.e., the user should be able to push Actor under their own account or under the organization.
The current workaround is to log out and call apify login with the organization token, but that is not comfortable.
There are multiple options. We could, for example, allow the storing of multiple accounts (profiles) in .apify/credentials file as AWS does: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html and allow people to easily switch between profiles.
Or we could add a parameter i (= impersonate) allowing to impersonate an organization in the command:
apify push -i=apify
The CLI would then fetch a user's token impersonating the organization and perform the command.
Activity
mtrunkat commentedon Nov 27, 2023
Link to feature: https://apify.productboard.com/feature-board/planning/features/24835644
[-]Apify CLI to support organizations the same way UI does[/-][+]Apify CLI to support organizations the same way Apify Console does[/+]B4nan commentedon Mar 11, 2024
Going through old issues and found #115 which seems pretty similar (feels almost like a duplicate).
edit: and also #94
patrikbraborec commentedon Jun 4, 2026
Consolidating multi-account/profile requests here — closing #94 (run with arbitrary token) and #115 (project-based config dir) in favor of this issue as the single tracker.
Planned scope (v1): named profiles in auth storage + a global
--profile <name>flag +apify login --profile <name>. Prerequisite: auth file structure redesign (#567). Full org switching and per-project config dirs are follow-ups.Note: stateless auth via the
APIFY_TOKENenv var (#720) already covers the CI/agent use case of acting as different accounts per process.mvolfik commentedon Jul 8, 2026
btw, I started some initiative around this in December which resulted in this Notion doc (and slack thread with some comments on it), but it never resulted in any code... It seems like this is going in the same direction (starting with named profiles in global auth storage), which is great, but I just wanted to link this, in case some of the product requirements/requests/ideas from there were forgotten :)
l2ysho commentedon Aug 28, 2026
I would like to start implement this along with #1328. I wrote down a wrap up section in https://app.notion.com/p/apify/CLI-auth-v2-2bcf39950a2280ffbda0fc9215fc0077 with my current idea based on all discussions and connected issues I was able to find. Feel free to drop a comment. cc @patrikbraborec @DaveHanns
patrikbraborec commentedon Aug 31, 2026
@l2ysho Thanks! I checked the document, and added two comments. I agree with you, let's do it as part of #1328.
patrikbraborec commentedon Sep 8, 2026
Consolidated into #1297, which carries the staged plan (#1383 to #1387). All context from this thread is copied there.