What are you trying to do? (please be as specific as possible and include relevant screenshots, code snippets)
We originally had ~5 seats taken by either developers or owners on the project but our free trial has since ended and our seat count has been dropped back down to 3.
The owner of our org is attempting to demote a developer from their current role down to a viewer so we can restore the ability to save our project. They are able to go to “Manage Organization” under the Org view and access the dropdown select for the user’s role. But, when attempting to change the value, nothing appears to happen and the value does not get updated even after refreshing the page. This is the same outcome on both desktop and mobile and across separate user experiences of others in the org.
What are the reproduction steps?
Log in as a member of our org with admin||owner||developer roles and navigate to “Manage Organization” under the Organization view. Find a user with the role “developer” and attempt to change their role to “viewer”.
Hey Jason! Thanks for your support here. My understanding is that editors (developer role) are seats that we fund. When did it change to include viewers? Is this recent?
Viewers have always counted as a seat. Unfortunately, our pricing page clearly doesn’t represent that correctly. I will fix the pricing page. Sorry for the confusion
Are you sure viewers were always a part of the seat count? I don’t feel like thats the case; especially since projects used to have the share by link setting as default selected. So, basically anyone with the link could view the project.
Viewers who use a publicly shared project will count as a seat and be added to the org without team-wide permissions. However, some of our logic there might be a bit wonky, and it may let you go over the seat limit in this case.
Ok, ya, I think something changed recently with how ya’ll do seating because that wasn’t always the case.
But that is good to know. I plan on doing some content creation and sharing of projects I’ve made, so that makes it clear that I’d need to self-host in order for that to be cost effective for me in my case.
I hear you all on the viewers. For now, I guess you can use the public link to work-around it temporarily. We’ll revisit how to handle viewers in our next pricing update.
