77 results found

1. We need to add the host racfid field to the Azure table data so that data lake condeco data and source applications data can be compared

   We need to add the host racfid field to the Azure table data so that data lake condeco data and source applications data can be compared

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Outlook Sign in URL

   Hi, It would be good if admins could prefill or define the Condeco URL for users and also remove the need for a verification email.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Allow PurposeOfVisit in Visitor_CreateVisitor_V1 API to allow other values

   The Visitor API has been designed to support UnKnown = 0, InternalVisitor = 1, ExternalVisitor = 2 and no other values. Suggest to enhance this feature as it does not make sense to have only 2 values accepted.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Allow PurposeOfVisit in Visitor_CreateVisitor_V1 API to allow other values

   The purposeOfVisit API has been designed to only support UnKnown = 0, InternalVisitor = 1, ExternalVisitor = 2. Does not allow other values to pass through which is quite cumbersome.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. API: Visitor Listener - Multiple Visitors in one notification and Multiple Ids for Visitors over multiple days

   Due to the way visitors are created in Condeco there is a visitor id / record created for everyday a visitor is visiting. This means any action will send multiple Ids in a single notification. Equally if a meeting is created and multiple visitors are created in that meeting, a notification is sent for multiple visitor ids for multiple visitors.

   In most use cases of the visitor listener I would imagine the applications they are posting to are doing some sort of deduplication of this data as they will only need one Id per visitor to retrieve their information. As there is no way from the visitor notification to determine if the ids are for multiple days of one visitor or many visitors of one meeting a workaround need to be put in place. This is to loop through the IDs getting the visitors name by the getVisitorsbyID endpoint and then checking if the current name is the same as the previous name. As names can be nonunique this is not a perfect solution. This solution also massively increases the API calls required

   This could be solved in a few ways:

   Firstly the listener could only post one notification per visitor. This would keep the idea of multiple ids for one visitor over multiple days however it would create a notification per each visitor created via the create meeting form

   If the above is not a potential solution a id could be added for each visitor so that they can be deduplicated based on this e.g:

   Multiple Visitors -
   [{'VisitorId': 1460985, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460986, 'Action': 1, 'VisitorNotifId': 1}, {'VisitorId': 1460987, 'Action': 1, 'VisitorNotifId': 2}]

   One Visitor over Multiple Days -
   [{'VisitorId': 1460985, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460986, 'Action': 1, 'VisitorNotifId': 0}, {'VisitorId': 1460987, 'Action': 1, 'VisitorNotifId': 0}]

   Due to the way visitors are created in Condeco there is a visitor id / record created for everyday a visitor is visiting. This means any action will send multiple Ids in a single notification. Equally if a meeting is created and multiple visitors are created in that meeting, a notification is sent for multiple visitor ids for multiple visitors.

   In most use cases of the visitor listener I would imagine the applications they are posting to are doing some sort of deduplication of this data as they will only need one Id per visitor to retrieve their information. As… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Provisioning of administrative roles (Global Admin, Country Admin e.g.) via API

   Currently, it is not possible to provide admin roles to users via external API (SCIM).

   Idea is to manage these over Azure/AD groups in the same way like group mapping for restricted ressources.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Provide location filter capability for all notifications, specifically visitor

   The API notification service allows for filters related to resource IDs, please provide the ability to filter for location ID too. Specifically for the visitor event (type 8), although seems like a great idea to do the same for other event types too.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Transfer QR code string via API HierarchyMapping endpoint

   We generate the QR string in our main data source. We would like to add the ability the transfer the QR code string from our main data source via the API into Condeco. This can then be used for desk/room check-in/check-out.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Accepted  ·  0 comments  ·  Ideas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Provide 'hot desking for phones' integration with Zoom

   Please see the link below from Zoom's product roadmap from April 2022. Zoom is coming out with features where folks can use their phone to temporarily connect to an office phone (someone else's with their permission, or a communal phone). Part of it is to show a location on a floor map. I checked Condeco's configuration guide and product roadmap and did not find anything on this topic.

   Please consider this integration for the future, see link below for more details.

   https://support.zoom.us/hc/en-us/articles/360043841032-Using-hot-desking-for-phones

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. OAuth Client Credentials - Westpac

    Condeco currently have API that requires authentication with OAuth 2 password grant type. Unfortunately, it is not aligned with Westpac Digital Platform (WDP) standards, as “PASSWORD” is not a supported grant type, and it is not secure (basic authorization which is passed in HTTP header). The requirement for Westpac is for Condeco to accept “Client Credentials” as the Grant Type.

    Due to this legacy grant type, Westpac have been advised by our Security architecture to get Condeco to uplift the grant type to accept “Client credentials”. This issue impacts the following API functions.

    1. Condeco Visitor API
    2. SCIM API
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Provide monitoring information regarding system health status

    To be update to date about the current system status is crucial to know about the latest status information for proper service provisioning. Otherwise end-users could not be informed in time in case of any system misbehavior.

    Therefore the system health status is needed for the admin - this should be provided either by an API or a monitoring dashboard (here at least e-mails to admins shall be sent, in case of an outage).

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. deactivate user visibility as default after user is created or imported in Condeco System

    Condeco is not using any automated process to provision users. Users either take the path of self-registration with SSO or a bulk CSV upload is done for this client to onboard new users. Condeco did an automation with Clops which does this update however due to caching issues this is not a successful solution to us. In order to mitigate this, Condeco was looking to explore the options available on our Admin API(APIM) endpoint for users however the attribute is not present on current build of admin API.
    Available today –
    {"users": [{"email": "string","userName": "string","title": "string","firstName": "string","lastName": "string","initial": "string","telephone": "string","mobile": "string","extension": "string","fax": "string","userRole": 0,"costCode": "string","deskSlotsPerWeek": 0,"userPin": "string","thirdPartyId": 0,"externalId": "string","externalSystem": "string"}]}
    We want to request to extend the attribute as its available in Users table update value of parameter 'hidedeskandworkstatus' to '1' in tbluser within the user’s endpoint.

    Condeco is not using any automated process to provision users. Users either take the path of self-registration with SSO or a bulk CSV upload is done for this client to onboard new users. Condeco did an automation with Clops which does this update however due to caching issues this is not a successful solution to us. In order to mitigate this, Condeco was looking to explore the options available on our Admin API(APIM) endpoint for users however the attribute is not present on current build of admin API.
    Available today –
    {"users": [{"email": "string","userName": "string","title": "string","firstName": "string","lastName": "string","initial": "string","telephone": "string","mobile":… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Ability to extract booking source for Personal Space via Condeco's API

    Right now, it is not possible to get datapoint around where the Personal Space has been booked from (Mobile, Web, Outlook Add-In, or Physical Hardware). Looking at adding this into the data source so that it is made available for extraction via API call.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Make Condeco Azure table storage work with Azure Data Factory

    As a Condeco customer, I'd like to integrate Condeco booking data with my internal data. Please make Condeco Azure table storage work with Azure Data Factory. Currently I can make connection to Condeco Azure Storage but cannot access data at table level.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Filter Room Availability results to only bookable rooms

    Currently, the GetRoomAvailability API has a UserID filter which can display rooms that only the user has visibility to. However, we have many rooms which the user can view but will not be able to book, as they are in restricted groups.

    Using this API, the full set of rooms are returned, even though many rooms are not bookable by the user, which leads to the user trying to book the room but unable to do so.

    The GetRoomAvailability API should have a filter like "onlyBookableRooms: true" which will only return rooms where the user has permissions to book the room. This will avoid showing users the unbookable rooms in search results.

    This impacts the new Condeco Unified Mobile App as well, as we tested that the unbookable rooms also appear in the search results in the Mobile App. However on the web portal, only bookable rooms appear in the 'Book a Meeting Space' feature.

    Currently, the GetRoomAvailability API has a UserID filter which can display rooms that only the user has visibility to. However, we have many rooms which the user can view but will not be able to book, as they are in restricted groups.

    Using this API, the full set of rooms are returned, even though many rooms are not bookable by the user, which leads to the user trying to book the room but unable to do so.

    The GetRoomAvailability API should have a filter like "onlyBookableRooms: true" which will only return rooms where the user has permissions to book the… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Allow GetUsers / GetAllUsers to filter by ResourceName / Username

    Currently the API for UsersGetAllUsersV1 only allows for obtaining CondecoID for user based on email address. Since a Condeco user's email address is editable via their profile page, it is not a suitable field to be used to map to Condeco ID. Existing we are using SCIM to sync new user accounts from ActiveDirectory to Condeco. It would be better to obtain CondecoID via ResourceName / Condeco Username using this API.

    Hence, can there be a /api/V1/users?resourceName=<user's condeco username>, so we can retrieve the user's Condeco UserID which is used for all other subsequent API calls like CreateMeeting etc.

    Currently the API for UsersGetAllUsersV1 only allows for obtaining CondecoID for user based on email address. Since a Condeco user's email address is editable via their profile page, it is not a suitable field to be used to map to Condeco ID. Existing we are using SCIM to sync new user accounts from ActiveDirectory to Condeco. It would be better to obtain CondecoID via ResourceName / Condeco Username using this API.

    Hence, can there be a /api/V1/users?resourceName=<user's condeco username>, so we can retrieve the user's Condeco UserID which is used for all other subsequent API calls like CreateMeeting… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Default floor and group in SCIM API

    Customers would like the ability to set default location values for users in the SCIM API. This would include not just the country and location, but also the floor and group. This would be on parity with the user important process for provisioning users in the application.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Retrieve all Users in a Group via SCIM API

    Customers would like the ability to retrieve the list of users that are assigned as members of a user group in the SCIM API.

    15 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. API get desk details

    While you can use the POST Desk API endpoint to create and modify desks, you are unable to verify the information that currently exists on a desk. It will help customers keep the desks updated with the right values if they can retrieve the current desk information. Information customers are looking for are:
    - External ID
    - Resource Group
    - Assigned User
    - Any other data element provided in the POST request

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. An API to delete a desk

    To support and automate the office reorganization process we urgently need the technical possibility to delete a desk by integration.
    Thanks

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Accepted  ·  0 comments  ·  Ideas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close