You are viewing limited content. For full access, please sign in.

Question

Question

workflow permissions and rights - Adding an account from another domain

asked on September 3, 2015

One of our clients said they had this working but was not sure how. Is there any way to add access to an account from another domain to allow them to manage the workflows on a workflow server.

They have the "Everyone" account in there with full permission which normally means that any account from any domain can have access but I found this was a default setting with Laserfiche. It does not actually allow Everyone to access the system.

 

0 0

Answer

SELECTED ANSWER
replied on September 10, 2015

Are we talking about the Everyone group on the WF server that's in the workgroup? That wouldn't include domain users. In a workgroup setup, you can only use the Designer on the same machine as the server.

0 0

Replies

replied on September 3, 2015

What is the trust relationship between the 2 domains?

0 0
replied on September 9, 2015

One is just on Workgroup. The user they would like to add is on a domain. Why doesn't the everyone account allow everyone to access it?

0 0
replied on September 9, 2015

Everyone refers to all the users in the current domain and trusted domains, it does not mean all domains because that would be a security hole if users unauthenticated to the current domain would be allowed in.

0 0
replied on September 10, 2015

The customer was sure they had this working. Does it not support allowing domain users when it is not on the domain?

0 0
SELECTED ANSWER
replied on September 10, 2015

Are we talking about the Everyone group on the WF server that's in the workgroup? That wouldn't include domain users. In a workgroup setup, you can only use the Designer on the same machine as the server.

0 0
replied on September 10, 2015

Yes, somehow they said they had it working. I suppose I will see if they can start using RDP and work directly from the server OS.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.