Управление правами доступа в co-managed IT

I haven't co-managed Ninja specifically, so take the tool specifics from someone who has, but the two things you named are where I've watched this go wrong regardless of vendor. With 20 techs across two orgs the permission model is the part that rots first, because roles get created per person during onboarding and nobody owns the mapping six months later. I'd write down who can do what by role before a single account exists, and settle up front which side owns patch approval windows, since that is the decision people actually fight over at 5000 seats. On the API side the rate limit is rarely the wall you hit first: the wall is a reporting integration that polls everything on a schedule instead of pulling deltas, and at their seat count that pattern will exhaust any budget you're given. Ge…