Happy to direct edit a change here, but using comment for now just to alert you and get the OK. Would like to change this from 'Customer' to 'Account' or similar, as we discussed. Would like to orient the survey as general question-response / communication mechanism rather than implying there's some sort of commercial aspect to it.

thanks, I filed ticket, I will do it as it requires a few changes around the place https://kanbanflow.com/t/tNePuSG3

FYI, thanks for raising this early. This is exactly what the monday meeting is for, small course corrections. Its not a big job to change this now, but if we had been minting access credentials for accounts and had the Survey filler app half done it would be a much bigger job. So keep raising things as you see them. Process improvement: I should have recorded it in Kanbanflow when you raised it monday but I forgot.

All users are allowed to delete other users?

no just admin users. The users provisioned in this page cannot use this page.

I pressed this button and the cell ran, but doesn't seem that anything new was logged into the notebook, as with previous buttons. Is this expected?

Ok - I see that the userAcccesKeys starts as an empty array, and then is populated with these two key objects the first time that one hits the button. Subsequently the buttons look like they run, but don't?

yeah in the console you will see the error "Uncaught (in promise) LimitExceeded: Cannot exceed quota for AccessKeysPerUser: 2"

After creating externally usable credentials, you still need to generate an access link (which can be independently revoked) https://observablehq.com/@categorise/survey-admin#access_link

I could use some help here. I am trying to succinctly describe what's going on for each of your high-level operations.

This is wrong:- "Create or delete a survey project—the constellation of users, groups, survey instances, and access linls that collectively comprise a survey." A project is just a survey. It has nothing to do with users. Users are an AWS concept. I am a little concerned that we try to write up what is essentially already written at the beginning of each section. And also that we reinvent the concept of a table of contents, when there already is an auto syncing table of contents at the beginning. If we write text here it is likely to go out of date, and also all the links don't work properly here.

ok I go with the flow, PTAL

I appreciate your view here and am happy to move this back out. Sorry that I get things wrong (and will continue to do so). I am trying to read straight through the document to understand what's being done or what needs to be done at each step (what we're configuring) when deploying. Please keep correcting me and letting me know where to move things.

I tried to delete 'freshNewUser' and got: `DeleteConflict: Cannot delete entity, must delete access keys first.`

That error message seems clear to me. Do you want it to cleanup its child resources as well (requires code). Put it in the backlog if so.

I think this should be moved to a technical setup document as its jsut confusing. This is more technical level, where as most of this notebook is about tool managment

actually I move it to AWS config

Thank you.

If a project is a survey, why not label the bucket 'survey'?

done!

I am a bit confused by the placement of this deploy button... It comes first before creating and selecting a project/survey?

This is to deploy the notebook 'app', its a level above specific surveys. Survey designer is used to design all surveys.

You mean this deploys the designer interface? I guess my question is: having not yet performed the operation to create a project (below), what am I expecting should happen here by clicking 'deploy'?

The application at https://d3f26ej57oauer.cloudfront.net/designer/index.html is updated (its linked above)

Leaving a comment to get notifications on future comments

I am getting a message here about not having a valid key pair. I am using my 'Aaron' admin credentials. I haven't assigned myself to the 'es1' project or 'es1_th' account, so maybe this is expected... just not sure how I'd move forward with this and the continued error messages below?

I seem to be able to login as you using the creds in https://observablehq.com/d/21350f4d369f6ec5?collection=@categorise/gesi-survey I jsut pasted the full key in there maybe try that?

Yeah, weird... I must have made a typo I couldn't see through the fuzz.

This refers to Amazon Cloud Front 'https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Introduction.html' ?