User Types

AppCentral supports different types of user accounts, each designed to serve a specific purpose within the platform.

• User: A standard account intended for individuals who interact with AppCentral services or features directly.
• Device User: An account type used for representing system-connected devices or background processes that interact with AppCentral in a limited or predefined capacity. These users typically do not log in through the standard interface but are essential for system operations or monitoring.

User

A standard user account intended for individuals who interact directly with AppCentral services and features

Device User

A Device User is a special user account type in AppCentral, intended for securely connecting SFM (Shop Floor Manager) devices with Made2Manage (M2M) systems on the factory floor.

Purpose

Device Users are used to manage shared SFM device access at work centers or pods. These accounts do not have access to standard AppCentral user features or administrative permissions.

How It Works

• Single AppCentral Login:
  Instead of creating multiple AppCentral logins for every SFM device, one Device User is created in AppCentral and registered with an email address, for example, [email protected].
• Mapped in M2M:
  In M2M’s User Management, the admin creates multiple SFM Device Users (e.g., Pod A1, Pod A2) and links each of them to the same AppCentral email address.
• Login Flow:
  When an operator launches AppCentral on a shared tablet, they log in using the Device User email (e.g., [email protected]).
  From AppCentral, they launch M2M.
  M2M then detects all SFM Device Users linked to that email and presents them in a dropdown list.
  The operator selects the appropriate pod or workstation group to begin the session in M2M SFM.
• Operator Clock-In:
  Individual operators then clock in separately using their badge or employee ID, just as they did in earlier versions of M2M.

Example Use Case

A tablet is mounted at Work Center A on the factory floor. The goal is to allow operators to access M2M through a shared device while maintaining accurate individual clock-in tracking. Here’s how the setup and usage work:

Setup by Administrator

• In AppCentral:
  The administrator creates a Device User account using the email address [email protected].
• In M2M:
  The administrator creates multiple SFM Device Users, such as Pod A1 and Pod A2, and links them to the same email address ([email protected]).

Operator Login and Pod Selection

• On the shared tablet, the operator logs into AppCentral using the Device User email.
• From AppCentral, the operator launches M2M.
• M2M detects the SFM profiles associated with that email and displays them in a dropdown list (e.g., Pod A1, Pod A2).
• The operator selects the appropriate pod or workstation group to begin the session.

Individual Clock-In

• After the session starts, each worker at the pod clocks in using their employee ID or badge.
• This setup enables shared access to the device while still ensuring accurate tracking of each individual’s time and activity.

User Roles

• Seed User Role: The initial administrative user created during system setup. This user has full administrative privileges and can configure the entire environment.
• Admin User Role: A user with elevated privileges who can manage users, groups, roles, and platform settings.
• Standard User Role: A general-purpose user with access limited to assigned roles and permissions. Typically used for day-to-day platform interaction without administrative control.
• Connect Admin User Role: A user with administrative privileges specifically related to managing AppCentral Connect features, integrations, or related modules.
• Community User Plus Role: A role that allows management of Aptean Connect users directly in AppCentral, aligned with Salesforce permissions.

Seed User Role

The Seed user is the initial user of Aptean AppCentral, responsible for activating, configuring, and accessing applications. This user is designated as an admin within the application.

Permissions

• Has full and unrestricted access to Aptean AppCentral.
• Can create, edit, and manage group authorizations under Access Management.
• Can grant Admin role privileges during user creation.
• Can delete an Admin user.

Admin User Role

The Admin role inherits the same permissions and administrative rights as the Seed user, enabling them to activate, configure, and access applications.

Permissions

• Has full administrative access to Aptean AppCentral.
• Multiple Admin users can be created.
• Can delete standard users.
• Cannot delete the Seed user.

Standard User Role

A standard user has basic access to the application and is typically used for routine or day-to-day tasks.

Permissions

• Access is limited to the applications explicitly assigned.
• Does not have administrative privileges.
• Cannot delete Admin or Seed user roles.
• If the user lacks access to an application, the Open button on the product tile is disabled, and a Talk to Admin button appears to request access.

Connect Admin User Role

The Connect Admin role provides Support Admin users with elevated permissions to manage support-related activities across all customer accounts.

Permissions

• Receive real-time notifications for all support case activity.
• View and manage support cases, including related Change Requests, Knowledge Base (KB) articles, and documentation.
• Access activity and audit logs for troubleshooting and monitoring.

Limitations

• No access to All Apps, Billing, Subscription, or User Management.

Deployment

• Automatically created for all new customer environments.
• Added to existing customer environments for consistent support administration.

Note: In the UI path (User Center > Access Management), if you do not see Groups and Users under the Access Management section, it indicates that your role does not have the required permissions to access these settings.

Community User Plus Role

The Community User Plus role extends user management capabilities in AppCentral to align with Salesforce permissions. This role allows organizations to manage Aptean Connect users and user access across supported products within AppCentral.

Permissions

• Modify Aptean Connect users directly in AppCentral.
• Access and manage user permissions through Access Management.
• Manage access for all cases and user-related activities.

Deployment

• A User Admin group is created during account setup to manage access across supported products.
• Community User Plus users can be added to both the Connect Admin and User Admin groups, enabling:

  • Full Connect administration.

  • General user access management.