Hi team!

I'm a part of CKSource team and would like to update information on our organization's page.
It seems that there's no way to give access from one org admin to another user, thus my request.

Thank you!

Comments

mdusza created an issue. See original summary.

vishal.kadam’s picture

Category: Support request » Task
Status: Active » Reviewed & tested by the community

To create or update an organization node requires a confirmed account.

The account has been already confirmed.

avpaderno’s picture

Status: Reviewed & tested by the community » Closed (duplicate)
Related issues: +#3443130: Request for 'confirmed' user role for mdusza

Confirmed by vishal.kadam on u/mdusza at 24 Apr 2024 at 15:55 IST

avpaderno’s picture

Status: Closed (duplicate) » Postponed (maintainer needs more info)

Actually, the project owner of the CKSource organization node is vokiel, who is the only person who can edit that organization node. Having the account confirmed is not sufficient to be able to edit an organization node.

Is there any reason for which the necessary changes cannot be done by vokiel? Keep in mind we do not change organization owner every time a different person needs to edit that organization node.

mdusza’s picture

The main reason is convenience and saving time to be honest as vokiel is currently not involved in Drupal-related projects within the organization.

However, I was unaware that it's possible only for a single person to be able to edit the org node.
I don't necessarily want his access to be revoked, so please ignore the request if there is no other option.

Thanks

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Postponed (maintainer needs more info) » Fixed

I apologize: I did not mean to not transfer the organization ownership; I just wanted to make clear that only a single person can edit an organization node.

Since vokiel is not involved in Drupal-related task, requesting an ownership change is correct. I changed ownership as requested.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.