Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 9 of 9

Thread: Admin permissions

  1. #1
    clane is offline Junior Member
    Join Date
    Mar 2009
    Posts
    5

    Default Admin permissions

    We are looking at the package for a client's e-commerce site but have some concern about the amount of control that the Admin user is given. So I have the following questions:
    Is is possible to have multiple admin logins
    Is there a way to provide different levels of permission to multiple admin users

  2. #2
    Mike The Last Boyscout is offline User
    Join Date
    Nov 2008
    Posts
    254

    Talking

    Yes. You can create multiple admin users and even restrict access to certain areas of the admin. Please see this article for more information about restricting admin access.

  3. #3
    clane is offline Junior Member
    Join Date
    Mar 2009
    Posts
    5

    Default Admin permissions

    Mike:
    That addresses part of the issue in that it allows you to remove view and edit apps but is there a way to provide access to some of these parms and not others?

    Many of these parms seem to be one that would prevent the system from running, while others like the number of sale items on the home page is one that we would like to customer's admin user to control from time to time.

  4. #4
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    Just create the 'restricted' admin user accounts as regular admins (not super admins). You can then edit the AppConfigs you want to deny them access to, and set the 'SA Only' field to 1 (true). Many of the more critical settings are already configured that way.

  5. #5
    Sennaya is offline Member
    Join Date
    Dec 2008
    Location
    http://www.ecscase.com
    Posts
    91

    Default Creating three Admin levels

    We need to create 3 levels of Admin.

    Customer Service Admin
    working only with Admin for Orders and Customers.

    Product Admin
    with only Admin for Product, Content and Organization.

    SuperAdmin
    to be able to do everything.

    I did not see these items in the menuData.xml file to edit

    We need the Admin dashboard to allow access for these three functions.
    Is there a way to do this?

  6. #6
    AspDotNetStorefront Staff - Scott's Avatar
    AspDotNetStorefront Staff - Scott is offline Administrator
    Join Date
    Mar 2007
    Location
    Ashland, OR
    Posts
    2,390

    Default

    You're not going to see "Content" in the menuData.xml file, you're going to see the string resource that generates that lable - admin.menu.content.

    There's no reason the directions linked before won't work. As they say, you might have to make a few small .aspx mods as well to further restrict things, but you can easily limit the menu options available.

  7. #7
    Sennaya is offline Member
    Join Date
    Dec 2008
    Location
    http://www.ecscase.com
    Posts
    91

    Default Horizontal menubar?

    The instructions say to edit the menuData.xml but I do not see calls for the items I mentioned. It looks like the same info as for the vertMenudata.xml

    <SiteMap>
    <item Text="(!menu.Home!)" NavigateUrl="default.aspx" LookId="TopItemLook"/>
    <item Text="(!menu.Categories!)" LookId="TopItemLook" />
    <item Text="(!menu.Sections!)" LookId="TopItemLook" />
    <item Text="(!menu.Manufacturers!)" NavigateUrl="manufacturers.aspx" LookId="TopItemLook" />
    <item Text="(!menu.CustomerService!)" NavigateUrl="t-service.aspx" LookId="TopItemLook">
    <item Text="(!menu.YourAccount!)" NavigateUrl="account.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.OrderHistory!)" NavigateUrl="account.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.FAQs!)" NavigateUrl="t-faq.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.PolicyReturns!)" NavigateUrl="t-returns.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.Shipping!)" NavigateUrl="t-shipping.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.Contact!)" NavigateUrl="t-contact.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.PolicyPrivacy!)" NavigateUrl="t-privacy.aspx" LookId="DefaultItemLook"/>
    <item Text="(!menu.PolicySecurity!)" NavigateUrl="t-security.aspx" LookId="DefaultItemLook"/>
    </item>
    </SiteMap>

    What I need to restrict for Admin is the horizontal menu bar for admin with Orders, Products, Organization, content, customers and Configuration menus in the Merchant Dashboard. Is it possible?

  8. #8
    Louie is offline Senior Member
    Join Date
    Oct 2008
    Posts
    126

    Default

    You overlooked the KB article. If you read the PROCEDURE carefully, it says "In the admin/skins/skin_1 directory there is a “menudata.xml” file. The one you've pasted here is from root\skins\skin_# directory.
    Last edited by ASPAlfred; 03-31-2009 at 08:23 PM.

  9. #9
    Sennaya is offline Member
    Join Date
    Dec 2008
    Location
    http://www.ecscase.com
    Posts
    91

    Default

    Thank you, that is it.
    And of course, everyone has renamed the admin directory for security, so it is in the renamed admin directory ...