Stefan Benz

Checked the logic, and yes this is the case, the OrgDomainVerifiedWriteModel does only process OrgDomainVerifiedEvent and OrgDomainRemovedEvent. Problem here is that we only have the domain to query the respective...

Normally the data should be as follows: - Company Org - Project - Project Grant - Customer Org - User - Authorization (Usergrant) for granted project What happened now: -...

> @stebenz I implemented partial updates for SAML and OIDC. I skipped API because it only has 1 parameter (Auth type) and it seemed pointless, because either you do update...

Through Actions v2 the API can be used to manipulate both creation and already existing user grants. So I will close this issue. If this does not solve the problem,...

@hifabienne The intention is that if you create a project there should also be a membership to determine at least one owner, comparable to the creation of an organization, then...

@reactima just to mention, there is already solution 2 in our example of [zitadel-go](https://github.com/zitadel/zitadel-go/blob/bfb0be051aebe56f349d7b60529f74727dc24c7b/example/mgmt/mgmt.go#L62), which is our go sdk. Unfortunately, your solution with the SQL will not work in this...

@adlerhurst and @muhlemmer how is it possible to add events without a resourceowner? Did we change this logic?

@muhlemmer @eliobischof Currently, for each package in which an integration test is implemented, we start a new server, create the clients, check if the machineusers exist, and create new PATs...

Hi @draeron I found some error message which got mixed up, but this situation is still a little confusing. First off, I created this PR [here](https://github.com/zitadel/zitadel/pull/8722) to correct the error...

@draeron Did you init and setup ZITADEL correctly as provided by our examples? You could also use our docker compose example to see if you did something different https://zitadel.com/docs/self-hosting/deploy/compose As...