To save everyone else the trouble, here’s a copy-and-paste of the AI transcript of the vide:
0:00
Hi everyone, this is Chandana, and I’m currently working as a product manager in the Forge team, mainly looking into the Forge Billing project.
0:08
As you all know from January 1st, the Forge’s resource usage would be counted towards Billing, and the first invoice would be generated for each developer space from February.
0:18
So as part of that we have already released cost dashboard and cost estimator along with the final pricing blog, and our next milestone stone is going to be developer space.
0:28
This developer space is very essential to generate the invoice and I’m seeking feedback from the community around the roles and permissions that we are planning to introduce at the developer space level.
0:39
Now these roles are on top of the existing app specific roles which currently exist like developer deployer viewer and all of that.
0:48
These are in addition to those app specific roles but at a developer space level. Now before going into the feedback I will share a brief on what is a developer space how can apps be associated to a space and what happens in the finance side of Now each developer space is a accumulation of all the apps
1:09
associated. already marketplace partners would vendor profiles they would automatically become developer spaces we are handling that mapping and all the marketplace apps were automatically be associated to that particular space.
1:24
Now to the same space you could allocate all your non-market place apps as well or you also have the freedom to create new spaces and allocate apps to those spaces as well.
1:35
So developer space is just a higher level hierarchy which you could group apps to the right spaces. So now how you could assign apps to a particular space, you would start doing it with a forge create or a register for all your new apps.
1:52
You could associate to a space that you are an admin of or you could even create a space and become a developer space admin of that space.
2:00
For already existing non market place apps, you would have a option in the console to assign it to the This is a view of all the apps and all the spaces that you’re part of.
2:12
You could also filter to a specific space and view all the apps that Yeah, so this is how the edition would look like at a developer space level for the rules.
2:24
Similar to how app specific roles work. we would be introducing developer space specific roles and you could add people to that space.
2:34
Now I’ll be walking everyone through the developer space roles and permissions we are planning. So the first person who creates the developer space becomes a developer space admin automatically.
2:48
They can go and add further more developer space admins to the developer space. And for already existing vendor profiles, what we will do is we will make all the admins over their automatically as the developer space admins.
3:06
So now what can a developer space admin do? Yeah, I’ll come to the app management side of things like you could add users to specific developer space roles.
3:18
You could create four jabs into the space. You could also assign unlinked non-marketplace apps into the space that you’re an admin of.
3:28
You could initiate the transfer of all these non-marketplace apps from one space to the other automatically from the console for marketplace apps or the existing ticketing mechanism would continue.
3:42
Developer space admins would automatically become the admin of all the four apps as first step that is what we are planning to release and I’m happy to seek feedback on if the community is okay in making them the app owners as well like as in they’ll be getting the app owner permissions as well which
4:01
is nothing but an additional three permissions which is delete the app if there are no installs transfer the app internally from one contributor to the other and yeah these are the main permissions that I’m seeking feedback on if The community feels the developer space admin should get inside an app
4:20
along with the app admin rule that we are anyways planning to release soon. Of course, deleting a developer space when there are no apps in it, you could also edit the developer space metadata such as name and logo.
4:34
You could also view the audit logs of 14 members or apps as well when an app got added and all of that, you would also get additional permissions if any from the marketplace site, which you already have in the vendor profile.
4:48
Currently we will migrate all those permissions as well. Now coming to the billing side of things, so consider a fresh developer space.
5:00
And the first person is going to create the app in the developer space that they are an admin of right as a because it’s a fresh space whoever creates the space becomes an admin and they’re also creating an app.
5:13
So what happens is when the first app is created by the first person they become a billing admin. So what can a billing admin do?
5:23
They can view all the invoices in the billing account. So for each developer space what we are applying to do is we will give a dedicated And in the billing account, you would be able to see all the apps that are part of the developer space.
5:39
You would be able to see the next bill estimate and the next bill date as well. Quotes is not relevant to forge, but billing profiles.
5:50
Yeah, a billing admin would be able to see everything here like the different invoice groups, which means different payment methods and the different apps associated to different payment methods could all be viewed here.
6:03
Yeah, a billing admin would be able to see all the payment methods associated to the developer space. Be it card, PayPal, ACH, Addresses, build to and ship to addresses would be able to be seen here.
6:20
Billing permissions is where the all the admins can be seen as well as there would be option for billing admin to add further more admins here as well.
6:31
There is another section called invoices wherein the monthly invoice could be accessed for all the apps in the space. So we will be providing a dedicated transaction account for each developer space and we will provide the hyperlink from the developer space itself.
6:55
So this is a view that could be accessed from the console. This will entirely be redirected to a billing account.
7:02
So I am seeking feedback on the following. So except the first person who creates an app and becomes a developer space admin and a billing admin, all the others would have of this permissions.
7:21
Like they will not be able to see the invoices, they will not be able to see the payment methods, addresses and all of that, but they could definitely see all the apps in the developer space and they could also view the billing admins and the billing account.
7:34
In order to get this billing admin permission, the first billing admin who has been there in the developer space would have to add others explicitly in the billing account so that they would get add-on permissions of all of these as well.
7:52
So I wanted to get feedback from the community on is this suiting to your use case is everyone okay with one person being a billing admin to start with and they will add further more people as billing admins to the billing account as they wish.
8:18
. Like what are further more roles and permissions you expect for a developer space? We are adding these additional roles to ensure that there are more controls around who is adding app to your space, right?
8:29
because each app would start getting cost incurred and it becomes important to put some gates at the developer’s base level.
8:36
So yeah, please feel free to share your feedback around this and I’m happy to get back on the revised roles and permissions based on the feedback.
8:45
Thank you.
It was more meaningful (to me) than a super-long summary. Perhaps next time, include a brief “executive summary” in the RFC description, and it might be a very good balance.