add user api ignores admin true parameter in body

in Mongo and waited till the screen refreshed

and it still does not permit the second member see the archive icon in the lower left of the board field when you hover over the board

so either the isAdmin attribute is not being read for members,

OR only the owner has archive/delete permission of that board

if so the api describes a string for an owner and an array for members

is there a way to have multiple owners of a board?

I mean the issue is three fold

a) new members created with the api get a isAdmin as false even if you include a isAdmin as true in the add user/member to a board

b) that if if you fix that and force isAdmin to true the second and later members do not get archive delete function (they may have permission but the GUI is not depicting the visual tools based on those permissions

c) if member permissions never extend to members but only the owner for archive/delete functions that means that only the owner can remove a board.

Though in many cases this may make sense, not being able to select this is more constraining then not getting PUT routines or webhooks for editing

If you want me to test things LMK. Right now I have mongo routines that reset isAdmin and others that turn off allows statements to block edit functions that are not supported by webhooks.

But I do not have a solution to not displaying icons for archive/delete or not overloading owner with atleast two users.

I have all that working just fine, so I can externally rename boards and swimlanes, change colors of swimlanes at creation or after the fact, changing board permission and user permissions, etc. So all that is good.

But this is the first time that the app GUI is not following the data in Mongo records

{ "_id" : "6ymKB5c4sgiwpoWYP", "title" : "Stimulus III", "members" : [ { "userId" : "3bNniN3P6DMdi9ziT", "isAdmin" : true, "isActive" : true, "isNoComments" : false, "isCommentOnly" : false, "isWorker" : false }, { "userId" : "MvkLYjA9Gxk4QoBDc", "isAdmin" : true, "isActive" : true, "isNoComments" : false, "isCommentOnly" : false, "isWorker" : false } ], "permission" : "public", "color" : "wisteria", "slug" : "stimulus-iii", "archived" : false, "createdAt" : ISODate("2020-04-10T17:19:33.170Z"), "modifiedAt" : ISODate("2020-04-10T17:19:33.272Z"), "stars" : 0,

"labels" : [ { "color" : "green", "_id" : "Ej3Wxg", "name" : "" }, { "color" : "yellow", "_id" : "LpGxup", "name" : "" }, { "color" : "orange", "_id" : "PFm9GH", "name" : "" }, { "color" : "red", "_id" : "nQ5h9E", "name" : "" }, { "color" : "purple", "_id" : "3xvxDD", "name" : "" }, { "color" : "blue", "_id" : "JKqZoT", "name" : "" } ],

"subtasksDefaultBoardId" : null, "subtasksDefaultListId" : null, "dateSettingsDefaultBoardId" : null, "dateSettingsDefaultListId" : null, "allowsSubtasks" : false, "allowsAttachments" : false, "allowsChecklists" : false, "allowsComments" : false, "allowsDescriptionTitle" : true, "allowsDescriptionText" : true, "allowsActivities" : true, "allowsLabels" : true, "allowsAssignee" : false, "allowsMembers" : true, "allowsRequestedBy" : false, "allowsAssignedBy" : false, "allowsReceivedDate" : false, "allowsStartDate" : false, "allowsEndDate" : false, "allowsDueDate" : true, "presentParentTask" : "no-parent", "isOvertime" : false, "type" : "board" }

Hmm. Well, there is isBoardAdmin and isAdmin. Depends is user admin of board or Wekan.

I think only BoardAdmin can archive board, not Normal/CommentOnly/NoComments/Worker

Normally in Wekan web UI you can change each member to be BoardAdmin or some other permission

I need to test and figure out what you mean

If someone has Normal permission, and that user creates new board, that user is BoardAdmin of that board

and can invite others and set permissions of that user