Sandbox

Hi,

I have a project in the Forge, and I placed a message inviting comment etc in the discussion section. Today I was just looking through the forge and noticed that there are no reply or new message buttons unless I am logged in. Is this correct, or am I missing a trick? Can end users who are looking for a component or who are having difficulty with a component, not post a message unless they too are developers?

I also noticed that by default the 'documents' section is inaccessible to casual browsers - again I may be missing something.  I did change the permissions on this one so that documents are accessible but I would have thought that the default should allow documents to be accessed.

Dean Marshall

DeanMarshall wrote:Hi,

I have a project in the Forge, and I placed a message inviting comment etc in the discussion section. Today I was just looking through the forge and noticed that there are no reply or new message buttons unless I am logged in. Is this correct, or am I missing a trick? Can end users who are looking for a component or who are having difficulty with a component, not post a message unless they too are developers?

I also noticed that by default the 'documents' section is inaccessible to casual browsers - again I may be missing something.  I did change the permissions on this one so that documents are accessible but I would have thought that the default should allow documents to be accessed.

Dean Marshall

You need to be a forge member to be able to post in the forge discussion area when the discussion is set at it's lowest level of permission - no anonymous postings possible from what I can see. But, you don't have to be a member of the project.

Defaults are, and should be set high first, then loosened according to requirements.

philmoz wrote:
You need to be a forge member to be able to post in the forge discussion area when the discussion is set at it's lowest level of permission - no anonymous postings possible from what I can see. But, you don't have to be a member of the project.

Defaults are, and should be set high first, then loosened according to requirements.

As a general principle start strict and loosen is of course correct. But for a public facing communication system this does, in my opinion, seem overly strict - and the fact that the looser option doesn't appear to exist strengthens my belief.

I agree that you don't have to be a member of the project to post - I was under the impression that 'casual visitors' couldn't register. I just checked back and it appears that they can - so I am not sure where I got that impression from - was it ever that way or is that just me. Probably just me 

The 'obvious' workaround then is to place a message on the discussion page telling people they must register before they can post.  I personally don't like such requirements - but I can live with them.

Cheers

Dean.

well, 'tis the same with this forum...
register to post.
Certainly, if they had time to synchronise logins before launching forge, then life would have been easier all round. 

Casual visitors... how many of us were casual before registering in order to start a project

You do not need to be a member of a public project to be able to post to it.

The project admin can set "default access permissions" so that no further role settings need be in place to allow "all logged in users" to post to forums within their project.

Now, since the permissions system is new to most project admins, I daresay some have not yet fully figured out how to tune their project permissions to meet the needs of users. Recommend that you mail them directly and make your request regarding posting to forums known.

Col