Assigning a contract to a subteam was supposed to give every member of that
subteam read access to it. Half of that worked: the contract showed up in your
contracts list. The other half did not — opening it, or acting on it, came back
as a permission error.
That split is why it was easy to miss. A list that shows the contract is the
first thing anyone checks, and it looked correct. The failure only appeared one
click later, on a record you had just been shown.
What you may notice
If a contract is assigned to a subteam you belong to, and that is your only
claim on it, you can now open it. Its contacts and its documents are readable
too, because those permissions follow the contract’s own.
Nothing changes for the claims that already worked — a contract assigned
directly to you, one you created, or one you collaborate on behaves exactly as
before.
What this doesn’t change
Subteam membership still grants read access only. It does not let you edit
a contract, delete it, or add notes to it — those remain limited to the
assignee, the creator and collaborators. Whether subteam members should be able
to do any of that is a separate question and has not been changed here.