It’s quite clear what the API key is for. The S3 Credentials are for the S3 gateway - that also makes sense. But I am failing to understand the connection between the S3 Credentials and the Access Grant.
I’ve seen an introduction where STORJ is being used via the S3 Gateway. That’s why the S3 Credentials were used. But in that video (and also in some documentation) it says to also create an Access Grant.
As a side note - if I maybe add some UX/UI observations:
Using the same wizard from all 3 buttons is a bit confusing.
I know the access type gets pre-selected, but yet I can click on “API Access” and switch it to create “S3 Credentials”. I suggest to either have one button to open the dialog or remove/disable the type selection in the box.
Also the “Name” placeholder is confusing. The title says “Name”, the placeholder is “Input Access Name”. While in hindsight it’s clear, better stay consistent between the title and the placeholder. It should be either “Name” and “(Input) Name” or “Access Name” and “(Input) Access Name”. Everything else is confusing - at least during onboarding of new users.
The placeholders are helpers, where we can give users examples, instructions, and guidance. It’s good practice to provide more information about the input field in the placeholders, because good labels are usually short and most users can benefit from this “extra” help.
I hear the confusion you reported. I’ll test your suggestions and see what users in general think. We’re testing our assumptions in all these iterations, so we’ll certainly be able to change them.
Would you like to be part of our selected group of testers? I’m frequently testing our design iterations before they go live through unmoderated tests on the Usertesting platform. It would be great to have your input before implementing our ideas! If yes, shoot me an email at email@example.com, and we’ll set up your participation.