Roster, fixture, practice, sponsor or player-payment behaviour received a material implementation update. Request, session, browser or abuse-protection handling received a material implementation update. The project designer, publishing pipeline or domain workflow received a material implementation update.
What users should notice
• Teams keep competition work and recurring player operations attached to the same organisation record. • The change strengthens the protection boundary without changing legitimate account permissions or product access. • A project remains attached to the same owner and project record from editing through publication.
How it works
• The update preserves team ownership and role-based access rather than creating automatic team records. • Security controls remain layered and server-enforced; public release notes never include rules that would help bypass them. • Publishing state is resolved on the server and access remains checked against project membership before changes are accepted.
Affected product areas
Platform services, Internal operations
Published on Discord by Ident.ink Bot.