Access Control Block (for your current Job)

About this utility :

Also see :

VIDEO

Project Transfer is used to pack a Job for transfer to another site. The Job has access control permissions applied and is also locked (" Lock project ") to make it unusable to anybody who does not have the proper password or the SDS2 viewer . That other site's administrator does have a password (and login name) which gives him permission to open the Job in SDS2 Model Review . When the other site's administrator opens Access Control , he unlocks the Job (" Lock project ) so that users at that other site can work in the Job. (Recorded in SDS2 Detailing , v2015)

page 1 | contents | home > utilities > utility functions > access control permissions | top


Introduction :

  • Options on the Access Control window apply to your current Job .
  • Since Access Control permissions govern accessibility to your current Job, they will be Packed with that Job if you do a Project Transfer . In other words, the permissions apply to both internal use of your current Job within your own computer network and to external use at remote networks where a copy of your current Job has been Unpacked and opened by an SDS2 program other than an SDS2 viewer.
  • Access Control does not password protect a Job viewed in the SDS2 viewer . You can safely use " Lock projec t " prior to sending a Job that is to be viewed with the viewer. This will help to protect that Job from being used for other purposes by SDS2 programs other than the viewer.
  • By setting strict Access Control blocking prior to Project Transfer , third parties can be prevented from accessing information that they do not have permission to access. For example, for a detailing group contracted to a fabricator, the detailing group might want to Project Transfer a Job to the fabricator for extraction of information such as CNC, reports and status. By restricting Access Control blocking on that Job so that outside networks are restricted to using SDS2 Fabricating to modify that Job, the detailing group helps to ensure that no further Modeling work is done on that Job by an outside network until the detailing group has been paid, at which time the Access Control Block can be changed and the updated model transferred (e.g., using Project Transfer ) to allow outside networks equipped with a full-featured SDS2 program to further modify the model.

page 1 | contents | home > utilities > utility functions > access control permissions | top


To open the Access Control window :

Case 1: To open the Access Control window for the first time, before a ProjectAdministrator has been assigned, choose Home > Utilities > Utility Functions > Access Control Block . You will be prompted to enter a password for " Access Control Block ."

VIDEO You may have to User and Site Options > Site > " Set access control block password " in order to open the Access Control utility for the first time. Your support representative can tell you what the password is. ( SDS2 Detailing , v2015)

Pressing the " Change Password " button on this window opens the Change Access Control Block Password window, which lets you change the password for your current Job only.

If you don't know the control block password, contact your support representative.

For additional information, see the documentation for User and Site Options > Site > " Access control block password ."

Case 2: If your Windows or Linux login name has not been added as a user in Access Control (but a ProjectAdministrator has been defined) and " Allow group permissions for any user not listed " is not checked, you will not have access to the Project. This means that when you Home > click the current Job's name > select that Project, you will be greeted by a message like the following:

Shown at left is the Access Control Station Error dialog. Pressing the " Permissions " button opens the Access Control Login dialog (shown below).

You will have to enter the " Login " name (" User ") and " Password " of the ProjectAdministrator or of a group administrator in order to open the Access Control window.

Once you are on the Access Control window, you can provide future access to the Project for yourself by adding a user , then entering your own Windows or Linux login name to that user's " Login " name.

Case 3: After your Windows or Linux login name has been added as a user, Home > Utilities > Utility Functions > Access Control Block opens the Access Control Login dialog, and you will have to enter the " Login " name and " Password " of the ProjectAdministrator or of a group administrator in order to open the Access Control window.

VIDEO Once a ProjectAdministrator is defined, a user trying to open Access Control Permissions is no longer prompted to enter the control block password, but instead must enter the password for the ProjectAdministrator or etc. (Recorded in SDS2 Detailing , v2015)

After a ProjectAdministrator has been defined ( case 1 ) and after you have been specified as a user in Access Control (as described in case 2 ), you can still get into Access Control from the Utilities Functions menu.

Case 4: Another way to open Access Control is to do so from your Windows operating system's Start menu. Just go to the Start menu, choose ' All Programs ' then choose the latest SDS2 software installation (e.g., ' SDS2 2021.08 '), then choose access control startup (e.g., ' SDS2 2021.08 Access Control Permissions '). You will be greeted by the familiar Access Control Login.

VIDEO A ProjectAdministrator added himself as a user then locked himself out of being able to use Utility Functions . Not a smooth move. Fortunately, as the video shows, there is a back door into Access Control Permissions -- through the operating system's Start menu. (Recorded in SDS2 Detailing , v2015)

If the " Utility functions " permission denies you access to the Utilities Functions menu, case 3 will no longer apply. To get to Access Control , you can still choose access control startup in your Windows Start menu.

------------------------------

Example 1: You are the ProjectAdministrator . As such, you have the responsibility to manage logins and passwords of all group administrators and are empowered to assign permissions to those groups. You should create groups for each organization that you anticipate your organization sending this Job to. For example, if you are sending your current Job to a fabricator whose computer network is independent of your computer network, you should create a group for that fabricator. Or, if you are going to be sending the Job to an engineering group on an independent computer network, you should create an engineering group. You should also create a group for your own organization and add the names of users within your organization who you want to give access to the current Job. If you do not enter a user's " Login " name, that user will not have access to the Job.

Example 2: You are an engineer with SDS2 Model Review . Your Windows network login name is Fred. A Job has been sent to you along with an access control group administrator " Login " name and " Password ." When you try to open that Job, you are greeted with the Access Control Station Error dialog ( case 2 ). You press " Permissions " then enter the " User " name and the " Password ." This opens the Access Control window, where you add a user named Fred. Now that your Windows network login name has been given access to the Job, you will no longer be greeted by the Access Control Station Error dialog when you start the Job. For getting to Access Control, case 3 will now apply to you.

page 1 | contents | home > utilities > utility functions > access control permissions | top


The ProjectAdministrator is the Job access control manager for all groups which are to have access to that Job. He or she has the responsibility to manage the logins and passwords of all group administrators and is empowered to assign permissions to those groups. The ProjectAdminsitrator sits at the top of the hierarchy which is the " Groups/Users " tree.

In this example , the ProjectAdministrator added three groups (detailingGroup, Fabricator and Engineer), each of which represents an independent Windows computer network.

Once you, the project administrator, have completed setting up Access Control , follow the instructions shown next to the information symbol (on the window) and copy the job_access file located in the Job's main folder.

The ProjectAdministrator is the person who adds groups ( ) that represent various computer networks which presumably will be granted access to the Job. The ProjectAdministrator 's own computer network may be represented by one or more groups, and each external network that will be sent a copy of the Job should be represented by a single group. When adding a group, the ProjectAdministrator assigns the group administrator for each network a " Login " name and " Password " and is responsible for communicating that login name and password to the individual who is the group administrator. For example, when a copy of the Job is sent to a particular group administrator (e.g., using Project Transfer ), the ProjectAdministrator relays that group administrator's login name and password so that the group administrator can access the Job. As shown in the example in the next section, the ProjectAdministrator has access to all group administrator login names and passwords on his or her own network, while the individual group administrator, at least initially, only has access to the name and password that the GroupAdministrator has provided for him or her.

The ProjectAdministrator may also choose to add users to a group that is within the computer network in which the administrator is a user. For example, in a network environment with multiple SDS2 Detailing stations, the ProjectAdministrator might be the team leader of the detailers charged with modeling and detailing the current Job, or the ProjectAdministrator might be the person who appointed the team leader. To ensure accountability and best protect intellectual property rights, the ProjectAdministrator should be one person only; that is to say, only one person should have access to the " Login " name and " Password " of the ProjectAdministrator .

The ProjectAdministrator should add users only to groups that are within the detailing group's computer network. Since only users that have been added to a group can have access to the Job, this means that if the ProjectAdministrator wants access to the Job, the administrator must add himself or herself as a user.

The ProjectAdministrator should not add users to groups on external networks. The adding of users to external groups should be done by the individual group administrators.

For the detailing group -- that is, the group that is on the ProjectAdministrator's local computer network -- the ProjectAdministrator may choose to set permissions for individual users to restrict them from performing operations that are outside of the scope of their responsibilities. Or the ProjectAdministrator may choose to delegate that responsibility to the detailing group's administrator. In some organizations, the ProjectAdministrator and the detailing group administrator may, in fact, be the same person, even though -- for the purposes of Access Control -- they have different login names and passwords.

For external groups, the ProjectAdministrator should apply Access Control permissions to the current Job in such a way that the Job can only be modified in permissible ways. This can help to ensure that the detailing group's rights to proprietary information are preserved and that Modeling work not yet paid for is not editable by those external groups or any third parties that may, for whatever reason, gain access to copies of the Job.

page 1 | contents | home > utilities > utility functions > access control permissions | top


An example :

This example shows that the ProjectAdministrator has access to all group administrator login names and passwords on his or her own network, while an individual group administrator, at least initially, only has access to his/her own login name and password, which was given to him/her by the ProjectAdministrator . For this example, " Allow group permissions for any user not listed " is checked off for all permissions.

The ProjectAdministrator , who we will call Floyd , adds three groups (detailingGroup, Fabricator and Engineer), each of which represents an independent Windows computer network. Floyd's Windows login name is Dave, so he adds the user Dave under the detailingGroup. This is the " Groups/Users " tree that Floyd sees when he presses " OK " to close Access Control .

The detailingGroup administrator is on the same computer network as Floyd and therefore could also be Floyd, but Floyd has given her a unique " Login " name and " Password ," so we will call her Barney . Since her Windows login name is Carol, she adds a user named Carol. She also adds a user named Frank. This is the " Groups/Users " tree that Barney sees when she presses " OK " to close Access Control .

Floyd also gave the Fabricator group administrator an unique " Login " name and " Password ." We will call that group administrator Goober . Floyd sends Goober a zipped copy of the Job via e-mail. When Goober attempts to open the job, Access Control requires that he enter the name and password that Floyd gave him. Since Goober will be the only person working in the Job and his Windows login name is Goober, he adds a user named Goober.

The Engineer group administrator we will call Opie . Floyd sends a copy of the Job to Opie along with the " Login " name and " Password " that Floyd assigned to the Engineer group. The illustration at left shows the " Groups/Users " tree that Opie sees when he first enters Access Control . Opie decides that, instead of using SDS2 Model Review , he will use SDS2 Viewer , which he has installed on his personal laptop, to review the Job.

When Floyd the ProjectAdministrator opens Access Control sometime after Barney and Goober have made their changes, Floyd is able to see the changes that Barney made, since Barney and Floyd are on the same computer network. However, Floyd cannot see the changes that Goober made since Goober is on a different computer network than Floyd.

page 1 | contents | home > utilities > utility functions > access control permissions | top


The Access Control window

---- The Groups/Users tree ----

Pressing the " Add group " icon adds a new group folder ( ) to the Groups/Users tree. Changing the " Description " changes the name of that folder. Before clicking the " Add group " icon, select the item in the tree you want the new group to be under. For example, select " ProjectAdministrator " in the tree if you are adding a new major group that represents an independent Windows or Linux computer network.

VIDEO A group is added and assigned group permissions. When a user is added to that group, the user inherits the group permissions. Additional access limitations can be applied to the user; however, the user cannot be given permissions that the group which that user is a part of does not already have. (Recorded in SDS2 Detailing , v2015)

Press the folder icon (the " Add Group " icon) to have a new folder ( ) appear in the tree. Enter a " Description " to change the name of that folder in the tree.

Pressing the " Add user " icon adds a new user to the Groups/Users tree. The user is added under the group that you selected before you clicked the icon. You should then select a Linux or Windows login name on the " Login " combo box menu to give that user access to the Job. Entering the " Login " name also changes the name in the tree. Note in the example shown below that the " Password " is grayed out (disabled). The Windows or Linux network password of a user is private (known only to that user) and should be kept that way to preserve accountability. When you add a user, that user inherits the " Permissions " that have been assigned to the group you selected when you pressed the " Add user " icon. You may, if you so choose, want to make changes to those " Permissions ."

VIDEO How to add a user. Be aware that it is often advantageous to add a group first, then add the user to the group. (Recorded in SDS2 Detailing , v2015)

Press the file icon to have a new user name appear in the tree. Enter a " Login " to enter change the name of that user in the tree.

Why add a user? Unless " Allow group permissions for any user not listed " is checked on, users must be added in order for them to access a Job using a particular " Station ." For example, if newt was not listed in the above example, newt could not use the " Stations " assigned to the group which in the above example is called "NameOfGroup."

Pressing the " Delete group or user " icon deletes the selected entry in the tree (along with its associated " Login ," " Permissions ," etc.).

VIDEO To clear the access control permissions that have been applied to a Job, simply delete the ProjectAdministrator . In other words, select " ProjectAdministrator " and click the trash can icon. (Recorded in SDS2 Detailing , v2015)

An alternative: If you don't want to permanently remove a set of permissions for a particular user, you can check the box for " Disable user ."


---- Project Information ----

Lock Project: or .

If this box is checked ( ), the current Job is locked so that no SDS2 programs other than an SDS2 viewer can open the Job. Any person opening that Job will need a password in order to open Access Control and unlock the Project.

If the box is not checked ( ), the " Permissions " that are entered will apply. A set of " Permissions " is entered for each of the various groups and users in the " Groups/Users " tree.

Tip: If you are transferring a Project for an outside office to review using the SDS2 viewer , you may want to " Lock project ," then open another Job and do the Project Transfer . This will make the transferred Job file unable to be opened by other SDS2 Programs. Of course, you will want to, on the original Job after Project Transfer , go into Access Control for that Job and " Lock project " to allow access to that Job at your own site.


---- Group Information ----

Description: A text string that describes the group. For example, if the permissions are being set up for an external group such as a fabricator or an engineering office, you might enter the person's name (spaces are allowed) or the name of the group. The " Description " for the ProjectAdministrator is hard-coded to be ' ProjectAdministrator '.

Allow group permissions for any user not listed: or .

VIDEO " Allow group permissions for any user not listed " is checked for a particular group. A user that is not listed under any group inherits the permissions for that group. (Recorded in SDS2 Detailing , v2015)

If this box is checked ( ), then the permissions for stations and permissions for functions that are assigned to the group that is selected in the " Groups/Users " tree will apply to users not listed in that group.

If the box is not checked ( ) for a particular group in the " Groups/Users " tree, the name of a user will have to be added to the group in order for that user to have access to the " Permissions " assigned to the group.

For multiple groups that are set to " Allow group permissions for any user not listed ," a user who is not in any of the groups will receive the permissions of the group that is highest in the " Groups/Users Tree ."


---- User Information ----

Login: The login name of the ProjectAdministrator , group administrator or user. For a ProjectAdministrator or a group administrator, this name can be a made-up name. For a user, this must be a user name on your Windows or Linux network.

The " Login " applies to the user (newt) that is selected in the tree. Note that since it is a user that is selected, no " Password " can be entered.

For the ProjectAdministrator , you can type in any name you like. The ProjectAdministor's name or "Administrator" would be a good choice. You will also need to enter a " Password ." The " Login " applies to the ProjectAdministrator when the top folder ( ) is selected in the " Groups/Users " tree. For the example above, " ProjectAdministrator " is not selected (newt, a user, is selected). Case 2 explains how this relates to logging in to Access Control .

For the group administrator, you can type in any name you like. Once a name and password have been entered, the name-password combination can be used to open Access Control . The " Login " applies to the group administrator when a folder ( ) other than the top folder is selected in the " Groups/Users Tree ." For the example above, it would apply if "NameOfGroup" was selected (which it is not). See case 2 for how this applies to logging in to Access Control .

For a user, you can select any of the Windows or Linux login names that are automatically populated on the " Login " combo box menu. The SDS2 data directory maintains a file listing all users that have run a program in an SDS2 installation, and it is that list that populates the menu. As shown in the example above, the " Password " for a user is grayed out (disabled) since Windows or Linux network login passwords are private. For a user to open the Access Control window, the user must log in as a group administrator or the ProjectAdministrator .

Password: A text string that you want to be used as the password for the ProjectAdministrator or for a group administrator. In the " Groups/Users " tree, the ProjectAdminsitrator is the top and a group administrator is any other than the top . This is the password that the administrator must type in order to open Access Control after access controls have been put into effect ( case 2 or case 3 ).

Disable user: or .

If this box is checked ( ), the user will not be able to use the program. In effect, the result will be the same as if you had deleted the user from the tree.

If the box is not checked ( ), the " Permissions " that are entered will apply.


---- Permissions ----

These permissions include permissions for stations and permissions for functions . To see the permissions for a particular group or user, select that group or user in the tree.

Copy permissions from: any user that is on the listbox menu. The menu lists the permissions for the group or for each user that is in the group (except the user that is selected to be copied to).

In this example, " Frank " is the user selected to be copied to. Frank is in the detailingGroup. Consequently, the permissions that can be selected on the " Copy permissions from " listbox are those for ' DetailingGroup ' and ' Dave ' and ' Carol '.

Full permission: or . This applies to the permissions of users or groups that are indented beneath the currently selected group in the tree.

Example : A ProjectAdministrator creates a group for a fabricator (called Fabricator ) and sets the permissions to be those shown above. The Job is later sent to the fabricator and opened in the SDS2 Fabricating program. The fabricator group administrator, after entering the supplied " Login " and " Password " for the Fabricator will have permissions like those shown on the right if the ProjectAdministrator turned off " Full permission ."

If this box is checked ( ), then all users indented beneath the selected name in the " Groups/Users Tree " will be able to turn on ( ) access privileges as well as turn them off ( ).

If the box is not checked ( ), then users indented beneath the selected name in the " Groups/Users Tree " will be able to turn off ( ) access privileges, but will not be able to turn on ( ) access privileges.


----- Permissions for Stations -----

VIDEO Permissions are changed for a user, resulting in that user being limited to only using the Modeling . (Recorded in SDS2 Detailing , v2015)

" Permissions for Stations " may be turned on ( ) or turned off ( ) for a group or user. They include " Detailing " " Modeling " " Drafting " " Model Review " " Fabricating " " Site Planning " and " Estimodeling ."

Detailing: or . Click here for a brief, one-paragraph summary of the capabilities of the SDS2 Detailing.

Example : The ProjectAdministrator sets up a group called detailingGroup to provide permissions for all users of SDS2 programs who are in that organization's computer network. The group has an SDS2 Detailing license and an SDS2 Model Review license. " Full permission " is given since it is anticipated that the group may purchase additional licenses at a later date.

If the box is checked ( ) and/or " Full permission " is on for a particular user, then that user will have Access Control permission to use the SDS2 Detailing program.

If the box is not checked ( ) and " Full permission " is off for a particular user, the user will not be able to use the SDS2 Detailing program.

Modeling: or . Same as " Detailing ," except that this applies to " Modeling ." Click here for a brief, one-paragraph summary of SDS2 Modeling.

Drafting: or . Same as " Detailing ," except that this applies to the " Drafting ." Click here for a brief, one-paragraph summary of SDS2 Drafting.

Model Review: or . Click here for a brief, one-paragraph summary of the capabilities of SDS2 Model Review (formerly called SDS2 Approval).

Scenario : The engineering group that you are a part of has the SDS2 Model Review program and has been sent an SDS2 Job. When you start up that Job, you enter the " User " group name and " Password " that the ProjectAdministrator sent to you along with the Job ( case 2 ). On the Access Control window, you find that you only have permission to use " Model Review ." That is to say, " Model Review " is checked and enabled while the other stations are not checked and grayed out.

Given the scenario above, your group is limited to using the SDS2 Model Review or an SDS2 viewer to review the Job. This is because the ProjectAdministrator elected to assign only " Model Reivew " to your group and turned off " Full permission ." At this time, you will probably want to add users to your group.

Other scenarios are many. The ProjectAdministrator may, for example, have turned on " Full permission " but only checked " Model Review ," which would mean that every " Station " would be enabled, but only " Model Review " would be turned on.

Fabricating: or . Click here for a brief, two-paragraph summary of the capabilities of SDS2 Fabricating.

Scenario : Your fabrication company has an SDS2 Fabricating program and has been sent an SDS2 Job. To review that Job, you need to enter the " User " group name and " Password " that the ProjectAdministrator sent to you along with the Job ( case 2 ), and which provide access to that Job exclusively via SDS2 Fabricating.

In the scenario above, you logged in as a group administrator for a fabrication group which has Job access limited to SDS2 Fabricating. You will probably want to keep " Fabricating " checked and add users to your group.

Another scenario is that you are the ProjectAdministrator . Under this scenario, you will want to check this box for any group which you want to have access to this Job via SDS2 Fabricating . If, for example, you were to turn off " Full permission " and check only the box for " Fabricating " for a particular group, then when that group administrator opened that Job and opened the Access Control window, only " Fabricating " would be checked and enabled, as shown in the example above.

Site Planning: or . Click here for a brief, two-paragraph summary of the capabilities of SDS2 Site Planning (formerly called SDS2 Erector).

Scenario : The structural steel erection company that you work for has the SDS2 Site Planning program and has been sent an SDS2 Job. To review that Job, you need to enter the " User " group login name and " Password " that were given to you ( case 2 ). As the screen shot at left shows, Access Control is set up so that only " Site Planning " can be used by your group to evaluate lifts and assign the to cranes for erecting the Job.

Given the scenario above, you will want to add users to your group so that they can use your company's SDS2 Site Planning program to review and modify that Job.

Another scenario is that the company you work for was granted access to all " Stations ." You should at this point add users to your group and check the box for " Site Planning " for those users who you want to grant access to that Job using SDS2 Site Planning.

Estimodeling: or . This program has most of the capabilities of SDS/2 Modeling, including the ability to import and export 3D models. It allows you to generate fast and accurate model-based cost and quantity estimates.

Scenario : The company that you work for has an SDS/2 Estimodeling station and has been sent an SDS/2 Job. The first time you open that Job, you are prompted to enter the " User " group login name and " Password " that were given to you ( case 2 ). When the Access Control window opens, you see the settings shown at left, as well as other settings. These settings mean that you can review the Job only by using an SDS/2 Estimodeling station (or an SDS/2 viewer ).

Given the scenario above, you will want to add users to your group so that they can use your company's SDS/2 BIM station to review that Job and import/export models to/from that Job.


----- Permissions for Functions -----

VIDEO " Full permission " is unchecked so that the user that is selected can be denied access to setup and utilities. (Recorded in SDS2 Detailing , v2015)

" Permissions for Functions " may be turned on ( ) or turned off ( ) for a group or user. They include " Job and fab setup " " Shape file edit " " Member delete " " Multiple model object edit " " Add material " " Override drawing editor " " Parametrics ability to run " " Utility functions " " Copy job setup " and " Copy fab setup ." Some of these " Functions " are similar to those on the Passwords list, but these " Functions " apply to your current Job as opposed to your office's computer network.

Member delete: or .

You have tried to delete members which access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, you will not be able to delete members in Modeling . For example, if you select a member and hit the Delete key, you will get a message like that shown above. This also prevents you from deleting a member using Mode > Member > Erase or Erase by Piecemark or Erase by Member Number .

Multiple model object edit: or .

You have tried to execute a multiple object edit which access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to multi-edit in Modeling . A message like that shown above will be displayed to that user when he/she attempts to edit multiple members or multiple materials or multiple bolts or multiple holes or multiple welds in Modeling .

Also see: This functionality is redundant to setting a " Multiple Object Edit Password " at Home > Utilities > Utility Functions . You may prefer to use the Utility Functions equivalent if it is available to you and you want to set up a network-wide password.

Add material: or .

You have tried to execute a function which access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to perform Model > Material > Add > ... operations in Modeling . A message like that shown above will be displayed to that user when he/she attempts to add material to a member.

Shape file edit: or .

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will still be able to open Shapes Properties . However, the editor will be read-only , meaning that the user will be able to use the editor for review only.

Also see: This functionality is redundant to setting a " Delete Password " at Home > Utilities > Utility Functions . You may prefer to use the Utility Functions equivalent if it is available to you and you want to set up a network-wide password.

Parametric's ability to run: or .

You have tried to execute a function which access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to perform Model > Parametric > Run. operations in Modeling . A message like that shown above will be displayed to that user when he/she attempts to Run a parametric.

Override drawing editor: or .

Drawing Editor restrictions from Dimension Settings setup :
  Lock outline layer   and/or
Lock manual editing of dimension text

If the box is checked ( ) for a particular user and/or " Full permission " is on, the user is permitted to " Override Drawing Editor restriction options " on a drawing (member or submaterial detail).

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to " Override Drawing Editor restriction options " on a drawing.

Job and fab setup: or .

You have tried to execute a function that access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to access setup. For example, when the user chooses a menu item from Home > Project Settings , the result is a message like that shown above.

Create new fab: or .

 Evudetailing_B1
 fabname_A (Master)
 fabname_B
 fabname_C
 Memberdetailing_B1
An example of a Fabricator selection dialog without a " New " button. Click here to see what this same dialog looks like with a " New " button. To open a dialog like this one, press " Change Fabricator " on the SDS2 Setup Job or Fabricator Options window.

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not have a " New " button to press when that user opens the dialog for selecting the current Fabricator. This also restricts the user from selecting ' Fabricators ' in the Copy Project Items utility.

Utility functions: or .

You have tried to execute a function which access control does not allow you.
   

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to choose options from Home > Utilities > Utility Functions . A message like that shown above will be displayed to that user when he/she attempts to do so.

Tip: If you have locked yourself out of access to the Utility Functions menu, you can still get into Access Control from the Windows Start menu. See case 4 .

Copy job setup: or .

If the box is checked ( ) for a particular user and/or " Full permission " is on, the user will be able to copy Job Setup Info using the Copy Project Items utility.

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to copy Job Setup Info using the Copy Project Items utility.

Copy fab setup: or .

If the box is checked ( ) for a particular user and/or " Full permission " is on, the user will be able to copy Fabricators using the Copy Project Items utility.

If the box is not checked ( ) for a particular user and " Full permission " is off, the user will not be able to copy Fabricators using the Copy Project Items utility.

page 1 | contents | home > utilities > utility functions > access control permissions | top