Showing an architecture to someone
There are three ways. They differ in what the other person can do and what they cost, so pick the one that matches how much you want to hand over.
Three ways to share
View (link)
Issue a link and pass it on. The recipient doesn't need to sign up, and it's free. You don't have to name anyone up front.
They can only look. No commenting, no editing.
Comment (guest, Team and up)
Name someone and let them comment on that one architecture. Available on Team and up. Guests don't use a seat, so there's no extra charge.
They can't see the other architectures in the workspace, and they can't edit. Guest slots are capped.
Edit (member, seat)
Bring them into the workspace as a member. This uses one seat.
Members can see every architecture in that workspace. The scope is the workspace, not a single architecture.
We don't accept "please let me edit" requests
Someone who opens a shared link can send a request to comment. They can't request edit access. That's deliberate.
Editing is a member's right, and becoming a member means every architecture in that workspace becomes visible. If one approval button on a link you sent to show a single architecture could hand over that whole scope, the person sharing would lose track of what they shared.
Who joins a workspace should be decided inside your organization, not by approving a shared link. IceShore doesn't make that call for you. When someone genuinely needs to edit, a workspace admin can invite them as a member.
Approving a comment request lets the person view and comment on that architecture. They still can't edit it, and they still can't see anything else.
Only an owner can change an admin
Every workspace has an owner — the person shown as "Owner" in the member list under workspace settings.
An admin can invite members and switch people between Editor and Reader. But only an owner can change an admin's role or remove an admin from the workspace. Adding a new admin works the same way.
Guest slots
Guests don't use seats, but their number is capped. The cap is seats × 3, with a floor of 3 when you have few seats.
At the cap you can't approve a comment request. There are two ways out.
Revoke a guest you no longer need
Free, and it frees a slot immediately. Filter the workspace member list down to guests and revoke from there.
Add a seat
Each seat adds three slots — but at 0 or 1 seats you need to go to 2 before the cap moves, because the floor of 3.
Architectures in a personal workspace
An architecture in a personal workspace is shared for viewing only. Comment requests aren't accepted, because a personal workspace can't hold members or guests.
To collect comments, create a workspace and move the architecture into it. You can do that from "Share via workspace" in the share dialog.
Still stuck?
If none of this fits your case, email support@iceshore.ai. We answer in Japanese and English.