Activity logs, access control, and day-to-day operational tasks.
Create a workspace, pick a plan, and get a team into it, in the order that avoids granting access before the storage and libraries are ready.
What each panel on the organization dashboard is telling you, and what to watch.
Stand up a workspace a team can actually work in, in the right order: storage and libraries before access, access before the first cluster.
Keep compute spend predictable without giving up throughput: what to check weekly, how to stop paying for idle clusters, and where to right-size.
Plans, accountability, and the questions worth asking monthly: who is spending what, which limits are close, and whether access still matches the team.
The terms this subject uses, defined.